SCOM provides rich override capabilities from the console so authorized users can override configuration such as thresholds, enable / disable or anything marked as overrideable. This allows customers to tune management packs as appropriate before or after deployment. There are times when people want to give some control of this away to the application or server owner and allow them to tune some settings at the monitored server.
This post walks you though the basic approach for using discovered properties for monitoring and refines this to avoid some pitfalls in real life.
This is more of a philosophical post I wanted to write based on some recent conversations I have had in my team when trying to educate some people on SCOM and management packs. There are different opinions on this and these are only mine. Feel free to disagree and feel free to post some comments if you do.
Within SCOM you have two overarching choices for monitoring – state based and stateless. Lets look at each and the benefits / drawbacks each one has and then I will get to the crux of things and why I think you should not try to force state based monitoring on something that you cannot really model the state.