Why does Threshold Monitoring become degraded?
search cancel

Why does Threshold Monitoring become degraded?


Article ID: 139139


Updated On:


CA Performance Management - Usage and Administration DX NetOps


Why is threshold monitoring constantly going into  degraded state?


Dx NetOps Performance Management any version


Really it comes down to resources for the Data Repository.  Also, things like the number of items being checked, the time window for the threshold rules, and also the number of rules play a role as well. The bigger the time window, the more data points we need to check to see if they trip the threshold. The more rules, the more queries we need to run against the DR. The bigger the groups where the threshold profile is applied, the more rows we need to examine. All which can cause more memory usage and CPU for the data repository.  Threshold profile functionality is driven through SQL calls to the DR.  Be mindful of the above factors to keep threshold monitoring from going into a degraded state and ultimately being disabled

Additional Information

Threshold Limiter Behavior