Building SCOM 2012 Dashboards

System Center Operations Manager 2012 has significant enhancements in the ability to display data through the use of its new dashboard technologies.
This post is the first in a series of dashboard-related posts introducing these new abilities. This post will create two dashboards:
– An VMM Host performance dashboard which contains the performance indicators of the Hyper-V hosts
– An Environment state dashboard which display’s the current health of the complete environments

SCOM 2012 Dashboards
Before we get into the steps of creating a new dashboard, I will talk a  over a bit of terminology. A dashboard is a collection of data from SCOM which give’s you the right overview on a specific view also named the Network Operations Center (NOC) display.

This shows the health of various key applications, products, or websites that are monitored by Operations Manager. Some Advantages of a dashboard:
– Ability to provide custom charts, graphs, beyond those available in the built-in performance view
– Network Operations Center (NOC) shows the health of various key products or applications
– Build an overview which covers the health of specific product’s

Let’s see how this actually all works…

Step 1 – We first start with the VMM Host Performance dashboard layout.
Note: The Virtual Machine Management pack is required for this dashboard

1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2012 management group.
2. In the Operations console, click Administration.
3. Choose the Management Packs node, click Create Management Pack and type the name (we choose Custom Dashboards) Click Next, Create
4. Go to Monitoring, go to the newly created MP name (Custom Dashboards), right click new, Dashboard view

5. Choose Grid Layout and click next, change the name in VMM Host Performance and click next, choose the 4 Cells option, choose next and create.

Step 2 – Adding Widgets to the dashboard.
1. Go to the Grid Layout and click to add widget

2. In the general properties choose the name of the Widget. We choose:
VMM Nodes – % CPU Performance
VMM Nodes – Memory Available MBytes
VMM Nodes – Logical Disk Reads/sec
VMM Nodes – Logical Disk Writes/sec

3. In the groups section choose Groups and scope it to Hosts in VMM, click next

4. Select the required Performance counters and click next

VMM Nodes – % CPU Performance 
Object:
HyperV Logical Processor
Counter: %Total Run Time
Instance (All)

VMM Nodes – Memory Available MBytes
Object:
Memory
Counter:
Available MBytes
Instance:
(All)

VMM Nodes – Logical Disk Reads/sec
Object:
LogicalDisk
Counter:
Disk Read Bytes/sec 
Instance:
(All)

VMM Nodes – Logical Disk Writes/sec

Object: LogicalDisk
Counter: Disk Writes Bytes/sec 
Instance: (All)

 

6. Click Next, set the time range to 12 Hours (or different)

5. Check the chart preferences and sort so it looks like this
Show the legend
Target
Path
Last value
Minimum Value
Maximum Value
Average Value

6. Click next and finish.
7. Do this for
VMM Nodes – % CPU Performance
VMM Nodes – Memory Available MBytes
VMM Nodes – Logical Disk Reads/sec
VMM Nodes – Logical Disk Writes/sec

 
Note;
HyperV processor monitoring; Why monitor HyperV Logical Processor, %Total Run Time and not the %Processor time

Measure overall processor utilization of the Hyper-V environment using Hyper-V performance monitor counters To measure total physical processor utilization of the host operating system and all guest operating systems, use the “\Hyper-V Hypervisor Logical Processor(_Total)\% Total Run Time” performance monitor counter. This counter measures the total percentage of time spent by the processor running the both the host operating system and all guest operating systems. Use the following thresholds to evaluate overall processor utilization of the Hyper-V environment using the “\Hyper-V Hypervisor Logical Processor(_Total)\% Total Run Time” performance monitor counter:
– Less than 60% consumed = Healthy
– 60% – 89% consumed = Monitor or Caution
– 90% – 100% consumed = Critical, performance will be adversely affected

See http://technet.microsoft.com/en-us/library/cc768535(v=bts.10).aspx for more information