Tag Archives: super metric

vRealize Operations 6 – how to add super metric to objects

The steps to create super metric changes quite a fair bit in version 6. I covered it here.

After you create it, you need to ensure it’s part of a policy. Otherwise, it will not show up in the object you applied to.

You can choose which policy you want to apply it to. In my case below, I chose the Default policy. I know it’s the default as there is a little D icon next to it, as you can see if you enlarge the screenshot. For the policy you’re choosing, ensure it covers the objects. You can see the objects covered at the lower pane of the screen.

Policy 2

You need to edit the policy. To do that, go to the Policy Library tab and find it. Click on the edit icon.

Policy 3

A dialog box will open. Click on step no 4 Override Attribute. Your screenshot should look like the one below.

Policy 4

Since there are many items shown, you want to filter it. Choose the Attribute Type, and deselect all except supermetric. As shown on the next screenshot, it has 1 supermetric that it not yet enabled. The status is Inherited.

Policy 5

To enable it, simply click on it, and choose Local. You can enable multiple lines.

Policy 6

And that’s all you need to do. Yes, I agree that the steps can be made easier.

As you can see below, it appears in the object that I applied it. In this example, I applied it to a cluster since this is a cluster level super metric.

Policy 7

Do not apply to object types that are not relevant, as it would show up in the objects. Notice the 3rd chart has a later starting time. This is because I created the first 2 supermetrics earlier (and enabled them earlier).

Standard Super Metrics

There are certain super metrics that I create in most installations. Their purpose is to quickly tell me the health of the environment. The questions I like to be answered are:

  • How well is my infra supporting all the VMs? I need the answer in terms of CPU, RAM, Disk and Network. So there are 4 separate answers needed. Just because the network is doing well does not mean the storage is. I’ve seen situation where ESXi host has plenty of RAM but not enough CPU.
  • How well was my infra supporting all the VMs? Same question as above, but I need to be able to go back in time. Just because everything is well on Sunday midnite does not mean it’s well on Friday 10 am. I need the data in a line chart so I can see pattern. I’ve seen daily pattern and weekly pattern.

To answer the above, I needed to create 8 super metrics

  • Maximum VM CPU Contention for all VMs
  • Average VM CPU Contention for all VMs
  • Maximum VM RAM Contention for all VMs
  • Average VM RAM Contention for all VMs
  • Maximum VM Disk Latency for all VMs
  • Average VM Disk Latency for all VMs
  • Maximum VM Network Dropped Packets for all VMs
  • Average VM  Network Dropped Packets for all VMs

I then apply those super metrics at cluster level. If the environment is huge with many clusters, I’d group the clusters based on their service tiers, and then apply the super metrics at the group level instead. The screenshot below shows the list of super metric that I have created. The one I selected shows it’s packaged inside a group package, as I apply it at the group level.

List of super metric

List of super metric

What does the formula look like? The screenshot below shows an example. This is a group level super metric, so I put “3” as a parameter. That means it has to go down 3 level from where it is being applied. I apply at a group level. The group is a collection of clusters. So the hierarchy looks like this: Group –> Cluster –> Host –> VM.

Super Metric at group level

Super Metric at group level

What about a metric that is applied at cluster level? Below is an example. In this example, I also show the preview feature. This is a very handy feature, as you can quickly test if your super metric makes sense or not. You can even look back in time. Notice the formula. There is something that is not required there. One of the metric is actually not useful. Can you tell which one? Hint: it’s about your vSphere knowledge, not vC Ops. Further hint: it’s about relationship between the same counter in VM and ESXi host.

Super Metrics at cluster level

Super Metrics at cluster level