Earlier Henk posted a nice article with regards to the Veeam nworks Management pack for System Center Operations Manager.

Time to take a sneak preview of the upcoming possibilities with Operations Manager 2012 and nworks. With System Center Operations Manager 2012 and the nworks management pack it will possible to visualize your VMware Service Levels agreed with the business owners.

This way your stakeholders will have always an accurate view of the services the IT department provides.

In our example we have defined 3 Service Level Objectives:

  1. ESX availability: ESX servers should be available for at least 90% of the time
  2. Memory usage: Taking into account the ESX memory optimization, we do not want to “spend” more then 150% of the physical memory on average of the time.
  3. CPU usage: ESX servers should not be using more then 80% of their CPU capacity

Let’s look how this actually works.

  1. Go to the Service Level Tracking (SLT) option within the authoring pane in the Operations Manager 2012 console and create a new SLT.
    image
  2. Give the SLT a useful name such as VMware Infrastructure Service Level
  3. Specify the class of object you want to target. In our case the target is “nworks VMware ESX Host Servers
    image
    As you probably know, do not store any SCOM changes in the default management. In this example we will store our SLT to the management pack SLTs
    image
  4. Now we need to “translate” our above described Service Level Objectives to Operations Manager language.
    We will start with the availability SLO, next is the Memory SLO and we will finish with the CPU SLO
  5. Add a new Monitor state SLO, give it a proper name, fill in the SLO goal (90%) and select OK.
    image
  6. Add a new Collection Rule SLO, give it a proper name, target MEMORY and select the collection rule HOST.Collect.memoryUsedPct. The aggregation method is of course Average and the SLO goal is less than 150.
    image
  7. Add a new Collection Rule SLO, give it a proper name, target CPUs and select the collection rule HOST.Collect.cpuUsedPct. The aggregation method is again Average and the SLO goal is less than 80.
    image
  8. We have now created our Service Level Objectives. Review the settings on the last step of the SLT creation wizard and select finish.
    image

 

To review your VMware Service Level you can use either the reporting engine (to schedule, publish,… the report) or you can go the monitoring pane.

Let’s start with the reporting pane:

  1. Open the Service Level Tracking Summary Report
    image
  2. Add the Service Level, define the timeframe and run the report
    image
    image

To view your Service Level in the monitoring pane, just go to the Service Level Tracking folder and review the Service Level generally or individual on a per Service Level Objective basis:
image

imageimage

Please note that System Center Operations Manager 2012 is still in beta phase, meaning that the Veeam nworks management pack is of course not yet supported on an Operations Manager 2012 environment and should not be used in production without notice.

The beta version of System Center Operations Manager 2012 can be downloaded here.
Veeam nworks can be found here, so you just download the bits and have fun monitoring!

Feel free to contact me on steven.duckaert<at>veeam<dot>com.