There are numerous instances when using SCOM2k7 SP1 it is appropriate to 'collect' Performance Data as reference data when troubleshooting or performing capacity planning for Windows Servers.  This Performance Data can either apply to an immediate circumstance (where typically creating a custom MMC using Performance Monitors and Alerts is acceptable), or in collecting Performance Data over a longer period of time for historical analysis.  In this Blog entry I will review setting up a Performance Collection Rule in SCOM2k7 SP1.  This Performance Collection Rule will specifically collect Performance Data for a specific Object and Counter as referenced in the Performance Logging and Alerts Microsoft Management Console (MMC).

Again, our objective - use SCOM2k7 SP1 to collect Performance Data on a specific Performance Object and Counter by writing a Performance Collection Rule in SCOM2k7 SP1.  In this example I use the 'Server' Object and 'Pool Non-Paged Bytes' Counter as the reference sample.


1.  Our Hyper-V Host for this configuration includes enough capacity to support our single server installation of SCOM2k7 SP1.



2.  In the Hyper-V Management Console I focus on the SCOM2k7 SP1 Server.  Numerous other Servers are running providing various Services.  Each Service (Server) is monitored using the SCOM2k7 Agent.



3.  As I begin I determine to use Performance Logs and Alerts reference library of Performance Objects and Counters.  I have found opening 'Perfmon' and targeting a specific Object, Counter and Instance assists with the SCOM2k7 SP1 Performance Rule configuration.



4.  The 'default values' appear as 'Perfmon' is opened.  Pay close attention to the 'Counter', 'Object' and 'Instance' fields for our reference values for the Performance Collection Rule.



5.  Here, the 'Server' Object and 'Pool Nonpaged Bytes' Counter is selected.  This Performance Object is referenced across any Server Role for both Windows 2003 and Windows 2008.



6.  Next, I move to the Monitoring Space in the SCOM2k7 SP1 Console.  Notice, when selecting the 'Rules' Management Pack Object by default the Scope is 'All Rule Objects'.



7.  Next, Scope the Rule Management Pack Object to only 'Windows Computer'.  This ensures that all Windows Computers receive the Performance Collection Rule.  If necessary, upon completion of this Performance Rule we could configure an 'Override' to exclude specific Windows Servers so only targeted Windows Servers receive the Performance Rule.



8.  With the 'Windows Computer' as the target, I instantiate creation of a 'New Rule'.




9.  In the 'Create a Rule Wizard' I focus the selection upon 'Windows Performance' as the Rule type.  Notice also the focus of the Performance Rule contents on the 'ITPS Lab Windows LOB Servers Managment Pack' (as opposed to the 'Default Management Pack'.)



10. It is important to correctly label this Performance Rule.  Also, my preference is to 'Disable' the Rule (the default is 'Enabled' for new Performance Rules) so as to allow a second review prior to enabling. Also, selecting to 'Disable' the Rule provides the ability to adjust any Override values to target Servers or Server Groups.  Additionally, notice the ability to 'Select' the Rule Target.



11.  The option to 'Select' the Rule Target provides the ability to again choose 'Windows Computer' as the target Server Group.



12.  With the 'Windows Computer' Group as the Rule Target the specifics of the Performance Objects and Counters can be selected next.



13.  Here we see the input fields for 'Object', 'Counter' and 'Instance' (along with 'Interval').  Again, I reference the 'Perfmon' MMC supplied values to ensure proper spelling and Object selection.



14.  The focus of the Performance Rule will include the 'Server' Object and 'Pool Nonpaged Bytes' as the Counter Object.  In this case, no 'Instance' value is defined. 



15.  The fields for the Performance Counter are updated and acceptance of the default 'Interval' of 15 minutes is approved.



16.  SCOM2k7 SP1 includes very granular data collection capabilities.  The tradeoff for granularity is more data.  The default values are acceptable for this Performance Rule.



17.  Upon completion of the 'Create Rule Wizard' displays our newly created Performance Collection Rule as 'disabled'.  Now, I begin 'double-checking' the input values for accuracy.



18.  The General Tab denotes the 'Rule Name', 'Rule Target' and 'Rule Category' (note, this Rule was left as 'Custom').




19.  The Configuration Tab denotes the internal database tables and values SCOM2k7 SP1 requires for a Performance Rule.



20.  No Product Knowledge is required for this Product Knowledge Tab.  This Tab allows Management Pack Authors to include pertinent factors or reference materials for future reference.




21.  Finally, the Overrides Tab provides the ability to View, Modify and Configure Overrides for this Performance Collection Rule.  No modifications are necessary for this particular Tab during this exercise.



22.  Upon review, it is now time to 'Enable' this Performance Rule.  Remember, since we Scoped this Rule to target the 'Windows Computer' Group, all 'Windows Computer' will receive this Performance Rule (Summary: All Servers will receive this!).



23.  Notice the Performance Rule is now 'Enabled'.  Since the Rule is configured to 'collect' Performance Data for our specific Object (Server Object and Pool Non-Paged Bytes Counter) every 15 minutes it will take a cycle or so (15 - 30 minutes) before data is visible.  Be patient.  (-:



24.  I move in the SCOM2k7 SP1 Console to the 'Computer's View.  This View (based on the SCOM2k7 SP1 Authorization Role) allows oversight of the 'general health' of all Servers monitored by SCOM2k7 SP1. 



25.  Here, selection of the 'Performance View' for a single server provides the ability to view the Performance Collection data from the new Performance Collection Rule.



25.  Selection of the 'Look For' drop down list offers the ability to search by text values.  Input of text like 'ITPS Lab' (which is the beginning of the name of our Performance Collection Rule) focuses the visible Performance Collection Data in the 'Performance View' Console.



26.  Success!  Our Performance Collection Rule has begun 'collecting' Performance Collection data for our configuration. 



27.  The tiny colored spec in the upper right hand corner of the Performance View console denotes a single 15 minute interval passing and a successful collection.  Over time this graph will mature and be stored in the SCOM2k7 SP1 Operations Manager Data Warehouse for a 365 day period (the default for the SCOM2k7 SP1 Data Warehouse is 365 days).  Useful information when referencing the Performance Values for each Server.



28.  Additionally, selection of the 'Show or Edit Rule Properties' provides a direct reference to the Performance Collection Rule just created.



29.  If necessary, upon confirming the Performance Collection Rule function the appropriate Overrides can be configured using the Overrides Tab.


In this scenario I have offered step by step instructions in how to configure a Performance Collection Rule in SCOM2k7 SP1.  This process could be used to 'collect' any Performance data for which Object, Counters and Instances are available. 

 If you'd like to 'Learn Advanced IT' - Check out the Free Video Lessons on Windows 2008 SP2 Failover Cluster Nodes for Highly Available File Services and other Microsoft topics as well -



Lynn Lunik
Chief Security Architect
IT Pro Secure Corporation

Blog Tags: Amazon Web Services, Forefront Client SecurityForefront Endpoint Protection 2010, Hyper-VVirtual PC 2007,  SCOM2k7, SQL2k8, Windows 7Windows 2008Exchange 2007, Exchange 2010Failover Clustering – ITPS, Failover Clustering – LL




No Trackbacks


No Comments