|
Choosing the thresholds mechanism mode
When you set up the monitoring of your environment with Monitoring Studio, you can set alert thresholds on various parameters. These alert thresholds typically depend on the application or devices you want to monitor.
Monitoring Studio uses a standard internal PATROL mechanism, often known as the Override parameters feature. It sets the alarm and warning thresholds you entered by setting a specially formatted variable under the /___tuning___ tree in the PATROL Agent configuration. This is the standard method to set thresholds and is supported by BMC Software since version 3.4.11 of the PATROL Agent.
With the 3.5 release of the PATROL Agent, BMC Software started to push another way to set thresholds, which is becoming the new thresholds standard in PATROL. This new method is known as PATROL for Event Management (formerly known as EventSpring) or PATROL Configuration Manager (PCM, formerly known as AgentSpring). Monitoring Studio fully supports PATROL for Event Management and is able to manage its thresholds through this new mechanism.
By default, Monitoring Studio uses the Automatic method. This thresholds mode detects the type of thresholds used by the PATROL Agent and sets the thresholds accordingly.
To choose the mode of Threshold Mechanism:
Right-click the main Monitoring Studio icon > KM Commands > Options > Thresholds Mechanism Selection.... The following dialog box appears:
Threshold Mechanism Selection — Default option
Select one of the three following options:
| • | Automatic: Monitoring Studio automatically detects the way thresholds are managed by the PATROL Agent and uses the correct mode, either Tuning or PCM, accordingly. This is recommended if you are unsure of the way thresholds are managed. |
 | When the Automatic mode is used, Monitoring Studio will select PCM/Event Management to manage thresholds if the "AS_EVENTSPRING" class is statically loaded or preloaded on the PATROL agent. Otherwise, Monitoring Studio will use the Tuning thresholds management mode. |
| • | Tuning: Monitoring Studio manages its thresholds through the standard Override parameters mechanism. Thresholds are stored in the PATROL Agent configuration under the /___tuning___ tree. This option is set by default and does not require any additional software. If you do not use PATROL for Event Management, it is recommended that you use this option. |
| • | Event Management: Monitoring Studio manages its thresholds through the Event Management mechanism. Monitoring Studio is fully compatible with this mechanism. All classes are provided without any pre-set thresholds. |
| Once you select the Event Management threshold management method, you can modify and manage your thresholds either through the Monitoring Studio interface, or through Event Management. Thresholds are stored in the PATROL Agent configuration under the /AS tree. This option requires that you set up the PATROL for Event Management KM on your PATROL Agent. PATROL for Event Management has to be enabled and preloaded. If you use PATROL for Event Management in order to modify or customize your thresholds, it is recommended that you use this option. |
 | In order to avoid side effects and unpredictable behavior, if you change the thresholds management option, Monitoring Studio will automatically migrate the thresholds set through the previous method to the new method (only for its monitored objects). That is: if you select the Event Management option, Monitoring Studio will automatically remove all the thresholds (set for its monitored objects) stored in the /___tuning___ tree in the PATROL Agent configuration, and set the same under in the Event Management database, under the /AS tree in the Agent configuration. |
| You may import a PATROL agent configuration (".cfg") with any type of thresholds. If necessary, Monitoring Studio will convert the thresholds to the type of thresholds currently used at the next discovery (within an hour). |
To Set or Modify Alert Thresholds
Monitoring Studio offers you full flexibility to set and modify the alert thresholds on each parameter.
Method (summary):
| 1. | Thresholds are set and modified through the Threshold wizard accessible by right-clicking the instance > KM commands > Set Thresholds. |
| 2. | Select the parameter on which you wish to set/modify thresholds |
| 3. | Select the threshold "type": Simple (2 alerts can be triggered) or Advanced (3 alerts can be triggered) |
| 4. | Select the type of Alert Action you wish to trigger when an alert is raised. |
For details, please refer to Setting or Modifying Alert Thresholds.
|
