Custom alert definitions trigger incorrectly after upgrade to Aria Operations 8.18.x
Article ID: 422960
Updated On:
Products
Issue/Introduction
Following an upgrade to Aria Operations 8.18.4 or 8.18.5, you may observe that custom alerts for CPU Usage % > 100 begin triggering for objects that were previously silent or expected to be excluded.
Environment
Aria Operations 8.18.4
Aria Operations 8.18.5
Cause
The triggering of these alerts is due to the activation of filter logic that was previously non-functional in Aria Operations 8.18.3 and older. A fix was implemented in version 8.18.4 to correctly evaluate symptoms where metric values (such as CPU Usage %) exceed 100. Because the logic now functions correctly, existing Alert Definitions containing this criteria will generate active alerts upon meeting the threshold, even if they did not trigger in earlier releases.
Resolution
Adjust and modify the custom Alert Definition or the associated Symptom Definition to apply the intended exclusion criteria or threshold.
Additional Information
Feedback
