Best Practice: MP should not use self-tuning thresholds


What does this best practice check for?

One of the types of monitors available in Operations Manager is the threshold monitor. Threshold monitors change state, and possibly alert, when specific thresholds are breached by whatever application component is being monitored. The best practice is to not use self-tuning thresholds, and instead use static thresholds which can be overridden by the end user to change the threshold value if needed.

Why is it important to follow this best practice? What is the impact of not following this best practice?

Self-tuning thresholds are known to create many problems for end-users as circumstances such as weekends or holidays, when application component usage may differ from a typical day, have severe effects on the thresholds when they should not.

How do I fix this in my MP?

Using the Authoring Console:

1.        When building a monitor that relies on thresholds, ensure that you choose the “Static Threshold” option.