A parameter is a command that periodically obtains data on a monitored system resource. Parameter data values are collected, summarized, and stored on the computer where the PATROL Agent resides. The collected parameter information is available for review by a PATROL console. The PATROL for Amazon Web Services organizes parameters into application classes by function or by the objects that they monitor. Several types of parameters are used and parameter history data is stored in a file.
You can use the attributes of a parameter to monitor and manage the parameter. An attribute is a characteristic that is assigned to a parameter. Parameters can have attributes such as scheduling, command type, and thresholds. An attribute can be defined globally for all instances of a class or locally for a particular computer or application instance. An instance inherits attributes from a class. However, an attribute defined at the instance level overrides inherited attributes.
You can use either the PATROL console or PATROL Configuration Manager to manage parameters.
The following table provides instructions to view various types of parameter data.
Type of data | Action required |
---|---|
Current data | Double-click the parameter icon. |
Data points | If a parameter graph generates annotated data points, double-click the data point to view the output. |
History data | All parameter history data is stored in a single binary file named param.hist, which is located in the following directory on the computer where the PATROL Agent resides: |
Warning or alarm state data | When a parameter enters a warning or an alarm state, PATROL usually generates a report automatically and displays the information in a task output window. View detailed information about a warning or an alarm in the PATROL Event Manager. Each warning and alarm from PATROL adds an event to the PATROL Event Manager. |
Follow these guidelines when you modify parameter properties:
This method takes advantage of the validations performed by the KM, and gives you the opportunity to verify that the changes perform as expected before deploying those changes throughout your environment.
KM Commands > Event Management > Parameter Settings > Status Flags > Set for Instances or Classes menu command from the Host icon
For more information, see the PATROL Configuration Manager User Guide.
Note
PATROL Configuration Manager rules that represent each parameter contain the _ANYINST_ designation for the instance name. The _ANYINST_ designation allows you to apply these changes to any agent host name without adding a specific agent host name to the rule for each parameter.
Drag the RuleSet to any agent host name where you want the changes applied.
Note
The following rule is created when you move the parameters to a RuleSet in PATROL
Configuration Manager: /AS/EVENTSPRING/PARAM_SETTINGS/STATUSFLAGS/paramSettingsStatusFlag” = { REPLACE = “2” }
This rule forces the account to apply parameter changes as soon as you apply them to an account or agent host name. If you do not want the changes to take place immediately, change 2 to 1, or remove this rule and reinitialize the agent for the account when you are ready to apply the changes. For more information, see the PATROL Configuration Manager User Guide.
As shipped, all of the parameters are active. To reduce the impact on your system resources and enhance performance, you can deactivate parameters that you do not need.
On the PATROL console, perform the following steps:
Add Comment