locked
Capturing all counters being collected by management pack RRS feed

  • Question

  • Is there a way within SCOM 2007 R2, to review all counters being captured by a management pack.  I am trying to create a report that would tell me from week to week how a computer is performing.  At this point, I am unsure wether the areas I want to focus on are being collected or not by SCOM.   Is there a simple way of reviewing each management pack and determining which performance counters are being collected by that management pack. 

    I could then create a pack with only the counters that are not being collected instead of recreating all the ones that are quite likely being collected already.

    If there is a simple way to do that - i'm pretty new to SCOM - please send me that technique.


    Thanks for your help,
    Daniel

    Monday, March 22, 2010 7:24 PM

Answers

All replies

  • Hi

    You can't really do this MP by MP in the console as the collection rules are targetted at classes - so you would do it class by class.

    You can use powershell to get a list of rules - the windows mp guide has an example at the end.

    You can also use SQL:

    http://blogs.technet.com/kevinholman/archive/2007/10/18/useful-operations-manager-2007-sql-queries.aspx

    See the performance section for a computer by computer breakdown and also performance signature section.

    Cheers

    Graham


    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Monday, March 22, 2010 7:38 PM
  • It isn't clear to me that collecting uncollected counters will help you figure out server performance.  Most counters are good for debugging specific situaitons and only cloud your view as an operator.  I do recognize the widely held belief that if you can see it you should collect it because someone really smart might be able to analyze it and tell us something.  The only outcome of that thinking I've ever seen is a budget request to the boss to keep buying bigger disks because we need more data.

    Advice: this is what I call "comfort data".  If that makes some readers uncomfortable, think about how you are using counter data and when was the last time it helped you.

    You can review each MP to see what it is collecting - but remember, the MP's are there to help you by weeding out the instrumentation that isn't relevant for operators.  Events are very much the same - very few events mean anything at all - so collecting them all is goofy.

    What you can do is go to the OS MP and look at the views it exposes for performance - if they are empty, enable the counter collection rules that drive the view.  Some thought has gone into each MP to help you understand the views (and thus counters) that should be useful for understanding performance.  You even get a nice graph.

     


    Microsoft Corporation
    Wednesday, March 31, 2010 3:56 PM
  • MP viewer is another tool that gives you an overview of an MP. http://blogs.msdn.com/boris_yanushpolsky/archive/2008/06/25/mpviewer-1-7-now-works-with-latest-e12-mp.aspx

    Again, be very specific about your scenarios, are there specific things you are trying to accomplish with the data collection.

    The OS MP already collects most of the basic stuff.


    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    Thursday, April 1, 2010 12:34 AM