Cloud Operations Tech Tips vCenter Operations vRealize Operations

vCenter Operations Management Tech Tips: Tip #27 1-Click Capacity Planning Dashboard – Part 4

In part 3 for this series we covered how to create the XML files needed for our 1-Click Capacity Planning Custom Dashboard. In this last part we will put everything to mix and create the dashboard.

The Dashboard Widgets

For this dashboard we will use 1 RESOURCES widget to show all our clusters and 4 METRIC GRAPH widgets which will use to show all the metrics and Super Metrics we added to the XML files.

01. Dashboard Widgets

Widgets Configurations

The first widget to edit will be the RESOURCES widget so it will show only “Cluster Compute Resource” Resource Kind. In order to filter the tag, under the “Select which tags to filter” select Resource Kinds > Cluster Compute Resource > All Attributes


As an added value, I’ve added two additional columns – one for cluster number of running hosts metric and one for running virtual machines metric.


For the METRIC GRAPH widgets, all configurations will identical except that each widget will show data for different capacity planning data set and will use its own XML file.

Change the widgets title and configure it so each widget will use its dedicated Interaction Mode XML file (no need to filter anything).

CPU CP Data (Last 30 Days)

04. CPU CP

Memory CP Data (Last 30 Days)

05. Memory CP

Storage CP Data (Last 30 Days)

06. Storage CP

Density and Deployment CP Data (Last 30 Days)

07. Density and Deployment CP

To show data from the last 30 days, change the “Date Controls” on each METRIC GRAPH widget.

08. Date

Dashboard Widgets Interactions

Remember our goal here to get all the cluster capacity planning data in a single click.

09. Dashboard HLD

The last part will be to configure dashboard widgets interactions so the RESOURCES widget will be the providing widget for all other METRIC GRAPH widgets.

10. Interaction Menu11. Interactions

Congratulations, you are done! Now all that is left is to select the cluster and get all the data coming from the XML files

12. Final Dashboard

Please send us your feedback and comments about this #TechTip below, as well as requests for #TechTips on other topics. And yes, follow us on twitter @vcenterops to get the latest on vCenter Operations and Cloud Operations Management topics. For a full list of all blog posts in the vCenter Operations Management Tech Tips series, search for posts with the tag ‘tech tips‘, or just visit


3 comments have been added so far

  1. Lior,

    Thanks. My first attempt at custom dashboard and got it working great with a single cluster. Really useful.

    I may be missing some obvious solution, but is this dashboard designed to work with only one cluster at a time?
    I have an issue extending the use of the dashboard beyond 1 cluster: The “dynamic datastore group” metrics & storageXML widget is hard-linked to particular cluster (“Cluster A” in your example) in this solution. So, if I chose another cluster, say Cluster B, in the “resource” widget, the “storage” widget does not get updated correctly to reflect the new chosen cluster. All other widgets (cpu/mem) update correctly. I have created “dynamic datastore group” and associated supermeterics for “Cluster B” (and other clusters), but not sure how to get the interaction of this dashboard to update the storageXML widget with new clusters (eg: “Cluster Bs”) metrics ?
    Hope that makes sense ?

    All I can think of is I have to build a separate dashboard for each cluster in my environment (which has dozens of clusters) , which is not practical , so I’m hoping that your solution can easily work with multiple clusters while including the storage reports.


    1. Thank you for your comment Michael!
      As far as monitoring shared storage you are still limited to the dynamic group. You have few options here:
      1. Create a dynamic group for all datastores (DAS incl.)
      2. Create a dynamic group for datastores with VMs files. If you have VM files on top of DAS datastores, those will be included in the group.

      If you have large a environment I would have go with the first option.
      Hope that helped!

Leave a Reply

Your email address will not be published.