Originally published here by Fran Martinez, May 25, 2015.
Thresholds are used to compare the sampled value of an attribute with the value set in the threshold. If the sampled value satisfies the comparison, an event is opened arriving to â€śEvent Statusâ€ť. The event closes automatically when the threshold comparison is no longer true.
it is what we called â€śsituationsâ€ť and they work in a similar way to the â€śprivate situationsâ€ť in previous versions .
The thresholds running in an agent are included in a .xml file located in
The thresholds for linux are included in:
The thresholds for windows are included in: c:\IBM\APM\localconfig\nt\nt_situations.xml
NOTE: the name can not be changed.
This doc. Cover the creation of a new threshold to monitor if the â€śnotepadâ€ť process is missed in a windows agent being monitored.
1. Open the APM UI : https://
2. Click in â€śSystem Configurationâ€ť + â€śThresholds Managerâ€ť
3. In our case, select â€śData Source Typeâ€ť = windows OS and click on â€śnewâ€ť to create our threshold.
4. Now , we have to set the name of our threshold, the severity, interval for testing of threshold (minimum 30 seconds, like the situation in ITM 6 ), the data set (it was called â€śattribute groupâ€ť in ITM6)
5. Clicking on â€ś+â€ť add our conditions and click ok.
6. Select the group or groups where we want to distribute the threshold. In this example , we have one a group created â€śmy componentsâ€ť which contains the windows agent to be monitoring.
NOTE: optionally , we can add a script or command to be execute on the monitored system when the threshold is true.
7. click on â€śsaveâ€ť.
8. Going to the monitored system and opening the file c:\IBM\APM\localconfig\nt\nt_situations.xml we are going to find that the threshold (situation) was added to the file with this format:
Now , our threshold is already distributed and running.
9. Once we stop the â€śnotepadâ€ť process the threshold is triggered and the event arrives to our APM UI.
Thanks for reading, Fran.