Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Controller (SaaS, On Premises)

Health rule evaluation with baselines and lookbacks


Health rule evaluation with baselines and lookbacks

I’ve discovered some unexpected behavior with AppDynamics in regard to how health rules are calculated when you have a fluctuating threshold.


Metric values for each minute are compared against the *current* threshold - not what the threshold was at the time the metric value was captured. This can become evident when you use baselines and standard deviations as your thresholds and you look back some number of minutes. Say you have a health rule that looks back 15 minutes. If you evaluate the health rule at 10:01, you're using the baseline from the 10:00 hour to evaluate metric values from the 09:00 hour.


Here's a screenshot to further explain:



Here’s the alert I mention in the above screenshot:


(I've edited out the server name from both screenshots)


Is this how health rules using baselines and lookbacks work across the board? Or is it only like this for Database health rules? And is this intended behavior? Is there any way to work around it?

By replying you agree to the Terms and Conditions of the AppDynamics Community.
Health rule evaluation with baselines and lookbacks