Tag Archives: vrealize operations 7.0

Your vR Ops. A bespoke operations tool

As human, we love tinkering. We customize our cars, our phones, etc. That’s why toys like Lego is hugely popular. In vR Ops, we recognise that each operations is unique. 100 companies may use the same identical architecture (e.g. they all use VMware on Amazon), but the way they run operations will be unique. While they are similar, at the ground level you will have 100 different operations.

One key feature of vR Ops is customization. One cloud provider customized by building their own UI. Another example of advance customisation is the vR Ops vCD Tenant App. You get a completely different app!

Now, you don’t have to spend that much engineering effort. Within a few minutes, you can customize vR Ops. I’ll show you one example, as this is a popular one among my customers.

In the above, my customers want to create a troubleshooting flow. It enables you to drill down by simply clicking on the object name. We leverage vR Ops ability to customize

  • the Summary Page.
  • the out of the box Dashboard.

So the implementation looks like this. We customize the Troubleshoot a Cluster Dashboard, and 3 Summary Pages.

Here is what the customized Troubleshoot a Cluster dashboard. You can access it via the Getting Started, because you’re using the same dashboard ID. Cool!

You can sort by any column. You can also change the time period (yes, no need to have Edit access anymore!). If you have 100s clusters, you can also filter to specific vCenter. Yup, these are new features in vR Ops 7.0!

Once you find the cluster you need, simply click on it. It takes you the Cluster Summary Page. I explained it here.

You can see whether the performance (read: high contention) is caused by high utilization or not. You can also see if the problem is spread across multiple hosts or not. From here, you can drill down into the Host. I explain the dashboard below here.

Finally, from the host, you can drill down into a VM.

The implementation does not use Group nor Policy. It’s certainly heavy on super metric.

You can download all the above dashboards from Sample Exchange. Hope that gives you an idea to customize your vR Ops to meet your unique operations. And have fun tinkering!

ESXi Performance Dashboard

vRealize Operations 7.0 enhances the widgets and dashboard, which enables us to create better user experience. With that, happy to share the VMware ESXi Performance dashboard:

The above dashboard is color coded. The idea is you just need to glance that everything is green. You only need to look at the counter if they are not green.

Layout wise, it’s split into 4 levels. Do click to enlarge it as there is description added on the image. The dashboard shows Performance first, then utilization. Can you guess why?

Performance: What counters define your ESXi Performance? 

  • We know that utilization is not performance. It’s related, but it’s not the same thing. An ESXi with low utilization could be a sign of something wrong. Could it be CPU and RAM are waiting for Disk? Could it be networks are dropping packets?
  • A high performing ESXi is one that does its job well. It serves its workload easily. It’s not struggling juggling the demands from all the VMs running on it. So performance must be measured in terms of how the VMs are being served. There are 2 sub-dimension to this.
    • How bad is the problem? This covers the depth.
    • How widespread is the problem? This covers the breadth.
  • How bad is the problem can be quantified by taking the worst CPU Contention or RAM Contention experienced by all the VMs.
  • How widespread is the problem can be quantified by the percentage of VMs facing contention.
  • The 2 sub-dimensions complement each other. It gives you an insight into the performance of your ESXi. If you have a very bad contention, but it only impact a small percentage, then the problem is narrow. This could be sign of monster VMs. If the worst contention is not that bad, but it impacts almost all VMs, then the ESXi itself is struggling.
  • Do you know why I don’t add VM Disk Latency? Even on vSAN, the solution may not be on the ESXi you’re looking at.

Utilization: Drive it high as you paid for the whole box

  • Now that you can measure Performance, you have confidence to drive utilization high. No need to artificially put headroom. Hence Utilization is shown below Performance as it’s secondary.
  • For RAM, both Consumed and Active are shown. If active is low, no need to upgrade RAM as Consumed contains disk cache. For me, it’s fine for Consumed to be 95% so long RAM Contention is 0.
  • For CPU, both Demand and Usage are high. Do you know the difference between both?


  • Download the dashboard from VMware code.
  • Import the dashboard, view, and supermetric.
  • Enable the supermetric in your base policy. Hope it’s a good introduction to the awesome power of supermetric!
  • Replace your ESXi Summary Page with this. Sunny my brother has documented here.

Hope you find it useful. Next is vSphere Cluster Performance dashboard.