If you still have noise at 4.01 - then the counter is not a good candidate for a STT and you should disable this - and create a static avg or consecutive sample threshold monitor.
But in this case i will need to create overrides for each server :(
I love the line:
"When you disable a rule or a monitor, you *NEVER* right click and choose "disable". "
Of course! Because that'd be WAY too obvious! Ha ha!
Yet another good post. This confirms what we suspected. Self tuning thresholds needs a collection rule as well.
We got a lot of errors after disabling the collection rules (as we didn't use those for reporting anyway), but it looks like we need to be a bit more careful when disabling collection rules.
For now we disabled the STT rules and monitors as well and let the server administrators decide whether they want them enabled again.
Hi Kevin, Are the learnt baselines lost if you restart the agent? Thanks, Roshan
the learned baseline thresholds are lost on agent restart, which means no alerting until another learning cycle completes again, making these types of monitors not very useful at all.