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 threshold limits.
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 ...Troubleshooting: Actions Not Executing on Alert Generation
When an alert is triggered but the corresponding action does not execute, the issue typically lies in configuration hierarchy, timing of association, or external delivery failures. Follow the steps below to identify the root cause. Step 1: Validate ...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).Can I configure thresholds & alarms to the apdex, response time metric that I have received?
Yes, You can configure thresholds & alarms to the below mentioned metrics. By default, Average data is fetched for last 5 minutes while applying threshold for the respective attributes. S.no Attribute Name Unit 1 Response Time ms 2 Apdex T 3 ...Troubleshooting: Alarm Not Generated for Threshold Violation
When a monitor attribute exceeds its defined threshold but fails to generate an alarm, the cause is usually related to data collection gaps, retry logic, or suppression rules. Follow these steps to diagnose the issue. Step 1: Verify Data Collection ...