I have noticed in my last few client environments that the same issue keeps occurring with use of the automatic baseline threshold calculations feature in SAM. The thresholds sometimes are pretty small and thus trip constantly. I would suggest providing some features to enhance the existing feature to provide control in the calculation method. Some idea are:
1. Provide the ability to dictate the precision of the threshold. (ie .00000 or .00)
2. Include an ability to configure a minimum value difference between the warning and critical ensuring you wont see a warning level of .1 and a critical value of .11. This would probably work best as calculated within a percentage. (ie. warning is some number, and critical is +25%)
3. Include the ability to configure the thresholds to calculated automatically and on a rolling basis. (ie, always the last 7 days from current time.
4. Add web based views to show the variety of thresholds calculated in a detailed yet concise fashion. Maybe web based reports out of the box?
I am sure others will comment and add their thoughts. I have been lucky to see this in a number of environments recently and thought it would be good to get the discussions going.
Thanks
Sohail Bhamani
Solarwinds Training and Professional Services
LinkedIN: Loop1 Systems
Facebook: Loop1 Systems
Twitter: @loop1systems