Threshold and availability for Agentless Server Monitor

Threshold and availability profiles help your configure thresholds to key performance metrics to receive notifications based on the criticality you configure. It also helps the alarms engine to decide if a specific resource has to be declared trouble, critical, or down. 

Add a Threshold and Availability Profile

1. Click Admin > Configuration Profiles > Threshold and Availability > Add Threshold and Availability.
2. Specify the following details to create a threshold and availability profile:
• Monitor Type: Select Server-Agentless from the drop down list.
• Display Name: Provide a label for identification purpose.
3. From the drop-down menu, choose the desired metrics for which thresholds need to be configured. Enter a value specific to the unit, and set the threshold conditions (<, <=, =, >, or >=) and the monitor state (Critical, Trouble, or Down) next to each metric. You'll receive alerts when these threshold conditions are violated.
   • General Attributes: Response Time, Packet Loss, CPU Utilization, Memory Utilization, Disk Utilization.
   • Interface Attributes: In Traffic, Out Traffic, Rx Utilization, Tx Utilization, Errors, and Discards.
   • Process Attributes: Process Memory, Process CPU, and Process Instance Count.
   • Disk Attribute: Disk Used 
   • Service Attribute: Service response Time
4. Advanced Threshold Settings (Strategy):
   Poll count serves as the default strategy to validate the threshold breach. You can validate threshold breach by applying multiple conditions (>, <, =, >=, <=) on your specified threshold strategy. The monitor’s status changes to ”Trouble or Critical”  when the condition applied to any of the below threshold strategies hold true:
   • Threshold condition validated during the poll count (number of polls): Monitor’s status changes to ”Trouble or Critical” when the condition applied to the threshold value is continuously validated for the specified “Poll count”.
   • Average value during poll count (number of polls): Monitor’s status changes to ”Trouble or Critical”, when the average of the attribute values, for the number of polls configured, continuously justifies the condition applied on the threshold value.
   • Condition validated during time duration (in minutes): When the specified condition applied on the threshold value is continuously validated, for all the polls, during the time duration configured, monitor’s status changes to ”Trouble or Critical”.
   • Average value during time duration (in minutes): Monitor’s status changes to ”Trouble or Critical”, when the average of the attribute values, for the time duration configured, continuously justifies the condition applied on the threshold value.
   
   Multiple poll check strategy will not be applied by default. During the conditions where no strategy could be applied, the threshold breach will be validated for a single poll alone.
   
   To make sure the condition applied on the strategy “Strategy-3: Time duration or Strategy-4: Average value during time duration” for threshold breach detection works as intended, you must ensure that you specify a time duration which is at least twice the applied check frequency for that monitor.
5. Click Save.

Edit a Threshold and Availability Profile:

1. Click the profile which you want to edit.
2. Edit the parameters which needs to be changed in Edit Threshold and Availability window.
3. Click Save.

Delete a Threshold and Availability Profile:

1. Click the profile in the Threshold and Availability screen which needs to be deleted. 
2. This will navigate to Edit Threshold and Availability window.
3. Click Delete.