Alarms are not generated and actions are not executed even when they are associated to an attribute of monitor.
Reason: Alarms and Actions will not be executed when the severity remains the same.
Solution: Alarms are generated and corresponding actions are executed if the severity changes (previous severity and current severity are different).
New to ADSelfService Plus?
Related Articles
Attribute violated threshold, but alarms were not generated
1.) Ensure that thresholds have been associated for the attribute and that there are no business hours restriction configured for it. For example, if the CPU utilisation of the server exceeded the permissible levels, navigate to Monitor → Configure ...Script/Custom Monitors - Alarms configured for Table rows were missing
In the Applications manager , users have the ability to manage the table rows of a script or custom monitor type according to their specific requirements. This can be done by enabling the "Enable Script Row Deletion" option. For example, let's ...Self monitor Applications Manager using Real User Monitoring
We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...I have created actions and threshold but I don't receive any alarms based on them.
Reason 1: The actions and thresholds are not associated with monitor to receive alarms. Solution: For more information, refer to Associating Thresholds and Actions with Monitor in the User Guide. Reason 2: The value of the metric has not crossed the ...