Written by Mark Farrugia, Senior Microsoft Premier Field Engineer.
In my previous post I started down the path of wanting to create some custom counters in Operations Manager 2007, but I could not get started until I had downloaded and installed the authoring console for Microsoft System Center Operations Manager (OpsMgr) 2007.
Now that that task was completed, let’s move on to creating the counters I wanted to get to. With the authoring console open let’s create a new management pack.
If a performance sample differs by the specified value (i.e. 10%), only then will the performance sample be forwarded to the Management server. Therefore if no sample is forwarded, the RMS assumes correctly that the value is within the specified threshold and will only update the next time a sample is forwarded. This methodology saves network bandwidth, and helps to reduce database bloat. The smaller the threshold number the more samples could get forwarded, the bigger the number the less number of samples, however performance data is more accurate with a smaller threshold. Therefore between the optimization settings and collection interval, Operations Manager gives you a great deal of flexibility on sample collection. The only one caveat to using this setting is that once it’s set, there is no way to change the setting through the authoring console. Click on Finish to save your rule.
If you are interested in sealing your management pack, an excellent blog post was written by another Microsoft Premier Field Engineer named Jonathan Almquist. You can find detailed instructions on Sealing a Management Pack on his blog.
Creating this management pack was an easy way to start introducing some concepts. As I continue to dive deeper into OpsMgr I hope to continue sharing some of what I learn with all of you.