In some environments, it is useful to be able to control the maximum size of the local repository to prevent a data or event “storm” from impacting performance. For example, if an agent computer is unable to connect to its management server for an extended period, it may generate a large number of redundant events that must be stored locally that you are not interested in transferring to the management server and repository when communication is restored. By limiting the size of the local repository, you can control both the strain put on the agent computer and the potential bottleneck involved in transferring a large number of unwanted events to the management server.
You can use the AMAdmin_SetLocalRPSize Knowledge Script to control the maximum number of events or data points that can be stored in an agent computer’s local repository. If the agent computer is not able to communicate with the management server, the local repository for the agent computer will store the most recent events and data points up to this limit until communication with the management server is restored.
NOTE:If the number of events or data points exceeds the limit you have set (for example, because of an extended network interruption), the oldest event or data records are lost as new events or data points are recorded.
In deciding how to configure the number of rows for events and data in the local repository, assume that 1000 rows is roughly equivalent to 1 MB. You should also consider the types of jobs you run on the agent computer and the frequency with which you collect data. In a typical environment, you are more likely to generate a large number of data points for reporting purposes than a large number of events. For this reason, you may want to reduce the number of rows you reserve for events and increase the number of rows you reserve for data points on some of your agent computers.
You can use the SetLocalRPSize Knowledge Script in conjunction with the AMAdmin_SiteSchedUpload Knowledge Script to establish a schedule for the communication between each agent computer and its management server. You can also use the SetLocalRPSize Knowledge Script in conjunction with AMAdmin_SchedMaint Knowledge Script to set storage restrictions on data and events when a computer requires maintenance or in conjunction with the AMAdmin_DisableSiteComm and AMAdmin_EnableSiteComm Knowledge Scripts when you need to temporarily disable network communication with the management server.
For more information about using any of these Knowledge Scripts, double-click the Knowledge Script in the View pane of the Control Center console, select the Values tab, and click Help.