Estimating the disk space on the Agent system for historical data

You can estimate the disk space required for 49 hours of historical data on your system. (The 49-hour time period is the default period specified in the file repository.cfg.) The units are in bytes. The formula provided here is an approximation; the best way to understand how much space your particular system requires is to check the size of your repository periodically.

The file is located in the following directory:

UNIX: $BEST1_HOME/bgs/mgroup/

Windows: %BEST1_COLLECT_HOME%\bgs\mgroup

The following formula applies to both Windows and UNIX. For UNIX computers, the value for the directory structure size is 750,000, as shown in the formula. For Windows computers, increase the 750,000 value to 850,000. This value is the estimated amount of space for the directory structure of an empty repository.

File space in bytes = 750,000 + nIntervals [BPA7510GS:36( nCPUs ) + 100( nDisks )+ (200) nFileSystems + 100( nProtocols ) + ( nProcesses)(176+ CommandSize )]

Component

Description

nCPUs

Number of CPUs

nDisks

Number of disks recognized by the kernel

nFileSystems

Number of file systems

nProtocols

Number of network protocols

nProcesses

Number of processes in the system process table

CommandSize

Average command size

For more information about estimating disk space for history data, see the following sections: 

Process and command size

The number 176 is the size of the data used to report on the process itself. The command size is determined by the average size of the command string. Generally, a command size of 256 is sufficient.

History space calculation example

The following values and calculation show how the formula is applied to approximate the space needed for an example system.

Number of CPUs

2

Number of disks

4

Number of file systems

14

Number of protocols

1

Number of processes

240

Command size

256

Number of intervals

616 (see following example)


File space needed = 850,000 + (616)[36(2) + 100(4) + 200(14) + 100(1) + (240)(176 + 256)] = 850,000 + 616 (160,812) = 99,910,192 (about 100 MB)

Back to top ↑

Number of intervals

The number of intervals are calculated by adding specific parameters along with their corresponding values to the Repository.cfg configuration file. The parameter values in this file can be edited according to the interval requirement.

Consider the following example where a portion of code from the configuration file is listed:

HISTORY
      SAMPLING_INTERVAL = 10
      LENGTH = 60
      SUMMARIZATION
         SUMMARIZATION_INTERVAL = 5
         LENGTH = 480
         SUMMARIZATION
            SUMMARIZATION_INTERVAL = 15
            LENGTH = 2400
         END_SUMMARIZATION
      END_SUMMARIZATION
    END_HISTORY

The syntax in the preceding code example is explained as follows:

SyntaxDescription
SAMPLING_INTERVAL = 10A 10-second data sampling interval
LENGTH = 601 hour of 10-second raw data
SUMMARIZATION_INTERVAL = 5A 5-minute summarized data spill
LENGTH = 4808 hours of 5-minute summarized data spills
LENGTH = 240048 hours of 15-minute summarized data spills

Back to top ↑

Impact of data collection on NT User Configuration metrics

Data collection in Microsoft Windows for the domain controller causes the NT User Configuration metrics to be extremely large in size, which can have the following effect:

  • High CPU utilization by the bgscollect process on the computer
  • Creation of large NT User Configuration UDR data files

To control the amount of data collected for this metric group

  1. Modify (or create, if one does not exist) the Collect.cfg configuration file so that it matches the following syntax:

    BEGIN_CONFIG
       BEGIN_NT_SYSTEM_COLLECT
         COLLECT_ALL_USERGROUP = FALSE
        MAX_USER_RECORDS = 500
       END_NT_SYSTEM_COLLECT
     END_CONFIG
  2. Restart the Perform Agent on the remote computer.

Back to top ↑

Control the size of Investigate history

This modified setting instructs the Collector to limit data collection to 500 user records on the computer. For more information about the Collect.cfg file, see Collect configuration file.

You can view Investigate history from the Gateway Server through the Investigate GUI. The default amount of Investigate history saved on the remote agent node is approximately 48 hours. You can adjust the value on the remote agent node to retain more or less history data. 

The amount of Investigate history is controlled by the Repository.cfg file. To modify the amount of Investigate history retained, refer to the following sections: 

Determining the amount of Investigate history to be retained

When determining the amount of history data to retain, consider the following values:

  • number of 10-second sample intervals
  • number of 5-minute summarized spills
  • number of 15-minute summarized spills

Investigate history by default retains:

  • 1 hour of 10-second raw data samples
  •  8 hours of 5-minute summarized spills
  • 40 hours of 15-minute summarized spills

These values are determined by the following entries in the Repository.cfg file:

 HISTORY SAMPLING_INTERVAL = 10
 LENGTH = 60 <-- This value is the number of minutes of 10-second samples.
 SUMMARIZATION
 SUMMARIZATION_INTERVAL = 5
 LENGTH = 480 <-- This value is the number of minutes of 5-minute summarized spills.
 SUMMARIZATION
 SUMMARIZATION_INTERVAL = 15
 LENGTH = 2400 <-- This value is the number of minutes of 15-minute summarized spills.
 END_SUMMARIZATION
 END_SUMMARIZATION
 END_HISTORY

Back to top ↑

Modifying Investigate history on a UNIX remote agent node

  1. Change to the $BEST1_HOME/bgs/mgroup directory:

    > cd $BEST1_HOME/bgs/mgroup
  2. Create a backup copy of the Repository.cfg file:

    > cp Repository.cfg Repository.cfg.sav
  3. Using a text editor, modify the following section in the Repository.cfg file to the appropriate values:

    # 10 second sampling interval
     # 1 hour of 10 second raw data
     # 8 hours of five minute summarized spills
     # 40 hours of fifteen minute summarized spills
     # HISTORY SAMPLING_INTERVAL = 10
     LENGTH = 60 <-- This value is the number of minutes of 10-second samples.
     SUMMARIZATION
     SUMMARIZATION_INTERVAL = 5
     LENGTH = 480 <-- This value is the number of minutes of 5-minute summarized spills.
     SUMMARIZATION
     SUMMARIZATION_INTERVAL = 15
     LENGTH = 2400 <-- This value is the number of minutes of 15-minute summarized spills.
     END_SUMMARIZATION
     END_SUMMARIZATION
     END_HISTORY
  4. Save the file.
  5. Stop the Perform Agent.

    > $BEST1_HOME/bgs/scripts/best1agent_stop -b $BEST1_HOME
  6. Restart the Perform Agent.

    > $BEST1_HOME/bgs/scripts/best1collect -B $BEST1_HOME -q

    The updated Repository.cfg file is read by the agent on startup, and the updated summarization interval options are active.

Back to top ↑

Modifying Investigate history on a Windows remote agent node

  1. Open Microsoft Windows Explorer and browse to the %BEST1_HOME%\bgs\mgroup directory.
  2. Right-click the Repository.cfg file, select Open With, and select a text editor.
  3. Modify the following section in the Repository.cfg file to the appropriate values:

    # 10 second sampling interval
     # 1 hour of 10 second raw data
     # 8 hours of five minute summarized spills
     # 40 hours of fifteen minute summarized spills
     # HISTORY
     SAMPLING_INTERVAL = 10
     LENGTH = 60 <-- This value is the number of minutes of 10-second samples.
     SUMMARIZATION
     SUMMARIZATION_INTERVAL = 5
     LENGTH = 480 <-- This value is the number of minutes of 5-minute summarized spills.
     SUMMARIZATION
     SUMMARIZATION_INTERVAL = 15
     LENGTH = 2400 <-- This value is the number of minutes of 15-minute summarized spills.
     END_SUMMARIZATION
     END_SUMMARIZATION
     END_HISTORY
  4. Save the file.
  5. Stop the Perform Agent by selecting Start > Programs > BMC PATROL > Perform > Stop Agent.
  6. Start the Perform Agent by selecting Start > Programs > BMC PATROL > Perform > Collect Data.
  7. From a collect process, select Query Information and specify the computer name of the agent computer to restart.
    A collect query is sent to the server, which restarts the bgsagent.

Back to top ↑

Related topic

Installing

Was this page helpful? Yes No Submitting... Thank you

Comments