@Mac.Newbold @John.Panelli and @Moe.Saidi : Thank you for weighing in here on this health rules topic. Let's continue to track this issue here.
A few general comments and tips on health rules (these don't necessarily solve your particular problem, however putting the general tips here for the sake of the Community to understand and maybe you find some value in these as well?):
-Tuning a large number of health rules is hard.
- values near 0 get tricky.
- The root of the problem may be a large number of business transactions.
- Maybe focus health rules by creating fewer of them, or only apply to a smaller number of critical metrics.
- Creating health rules is an iterative process. It's okay if things aren't perfect at first, or not everything has granular metrics, as long as we continue to improve them.
Workaround suggested from an AppDynamics consultant:
For this reason, I generally refrain from alerting purely based on baseline, one option is to create a composite health rule with: 1. Load as a criteria , Calls/Min > some meaningful value 2. Baseline > Meaningful 'x' deviations 3. Slowness Indicator : {slow+verslow calls}/Total Calls/Min*100 . This helps to say 'Alert me only when breach of the baseline impacts 'x' % of the users'
... View more
