How to create simple Heat maps in vRealize Operations manager 6.4.0.

I have been playing with the dashboards for a while and wanted to show to you how to create Heat Maps in vRealize Operations Manager. Heat Maps are really good because they can  combine two metrics together and give a good idea of how each metric is with respect to the other. For example, In Virtualization Storage technology, you can try to see how your datastores are doing with respect to the volumes they are on. In this post I am going to be focusing on Datastores inside of Flash arrays Volumes. These volumes are on PureStorage flash array.

Let me get into the details so you can understand better. I am using vRealize Operations manager Version I am using PureStorage All Flash Arrays in this example. So lets start the designing our dashboard.

After you have successfully logged into the vRealize Operations Manager. Click on Home and then Click on “Actions” and Select “Create Dashboard”. You will see the following pop up window come up.


Give the dashboard a name like “FlashArray Volumes Vs Datastore Heat Map” in the “Name” Field. Now click on “Widget List” in the above window. Click on “Heat Map” widget and drag it to the right as shown below.


Once the “Heat Map” widget is there, we need to configure the widget.


Now you are going to be in this screen. Give the Heat Map a meaningful title like “Volumes vs Datastore Heat Map”.


After giving it a good title like “Volumes vs Datastore Heat Map” we have to give it a Meaningful name. This name will be the name of one of the configuration which we can have in a heat map. For example, in one Heat Map configuration I will be using the “Datastore I/O|Read Latency (ms)” and in the same heat map using I can use another configuration like “Datastore I/O|Write Latency (ms)”. We can have several configurations in a heat map. This will become more clear as I go along.

So, Now I will give the name “Read Latency.


Now we have to group these Datastores in groups of FlashArray volumes. So now we have populate the “Group By” field. I click on the Downward arrow as shown below in the “Group By” field.


Then I clicked on Right Arrow next Pure Storage Adapter as shown below.


I selected the PureStorage “FlashArray Volume” as shown below.


Now we have selected the FlashArray Volume as teh object we are going to be groping all the objects. Now our next task is to select “Object Type”. We will click on the Downward arrow next “Object Type” as shown below.


Now we are choosing the Object Type to be “Datastore” which is under “vCenter Adapter” as shown below. So, we click on vCenter Adapter as shown below.


Now when we see the list of objects under vCenter Adapter we will select “Datastore” object by scrolling down to it.


We are now going to select “Datastore” Object as shown below.


Now we have selected “FlashArray Volumes” to group by and selected “Datastore” object as the type which is going to be inside the FlashArray Volumes as shown below. Our next task is to select a appropriate metric to size the Datastore Objects.


Now I click on empty box in the “Size By” Field as shown below.


Once I click on the Empty Box in “Size By” field, I will see a list of metrics as shown below. But I clicked on the Square Box next to “Capacity” as shown below.


Once I clicked on the Square Box next to “Capacity” I am going to see all the metrics related to Capacity for the “Datastores” object. For this example, I chose “Total Capacity (GB)” but you can any other metric you want. You have to double click on  “Total Capacity (GB)” metric to select it.


After selecting “Total Capacity (GB)” metric for “Size By” field, we only have one more metric to select for the last field which is “Color By” Field.


In order to select the Metric for “Color By” field, we have click in the empty box next to “Color By” field as shown below.


Once you click in the Empty Box next to “Color By” field you will see metrics related to Datastore object. I selected “Datastore I/O” as shown below by clicking on the Square box.


Now you can see all the Metrics related to “Datastore I/O” as shown below. I selected “Read Latency (ms)” as shown below, but you can select any metric you want.


Now lastly we have to make sure to enter meaningful values to indicate minimum and maximum values for read latency. If you don’t enter values here, vRealize Operations Manager will autoscale the values for you which might give you unexpected results.


I filled out “0” for Minimum value and “25” for Maximum Value, and then clicked on “Save” below to save the Heat Map configuration.


Now click on DashBoard


Now click on “+” sign next to “DashBoard Navigation” as shown below. This step will ensure where this Dashboard will be showing up in your vRealize Operations Manager.


Now click on the Drop down arrow as shown below. Now you will be given choices as to which tab, you would like to place this dashboard.


I selected “Home” tab as shown below.


Lastly you can click on “Apply Navigations” as shown below and this dashboard will be placed in the Home tab.


Now you can save the Heat Map in the Dashboard by clicking on “Save” as shown below.


Now if you go to Home and then click on “DashBoard List” as shown below, you will be able to see your Dashboard you just created as shown below.


This is the end of creating a Heat Map in a Dashboard in vRealize Operations Manager.

In my next blog posting I will be adding another widget to this dashboard which will give us an insight into what Virtual Machines are running on this datastore.























How to create super metric in vRealize Operations Manager

This is my first blog posting. I have been using vROPs for some months now and I will be showing you how to create a super metric in this blog posting. I am going to be using PureStorage FlashArrays for this task.


I will be designing a simple SuperMetric. The problem I am trying to solve here is to calculate Average Latency. I have both the read and write latency on a volume on PureStorage flash array but I am missing “Average Latency”. This is where I can utilize Super Metric, since a super metric can use simple metrics to create a new metric. I am going to be adding read and write latency together and taking a Average to create a new metric called “Average_Latency”. This is a good use case for creating super metric.

I am going to use the simple sum function in super metric to combine “Read Latency (us)”and “Write Latency (us)” metric together, since we do not have that metric available to us in vROPs for Flash array volumes. I am going to name this Super Metric as “Average_Latency”.

Login to your vRealize Operations Manager (vROPs) instance.


Click on Content -> SuperMetrics


Now I am going to walk you through the steps of creating your own supermetric. I am creating this super metric on flash array volume but you can choose any other object type as well.

Click on “+” sign to create a super metric.


You will see this pop window come up.


Click on “Function” as shown below and Select “Sum”


Click on “Operators” drop Down menu as shown below and select “(“ parenthesis.


Now click on Object Types as shown below and select “Pure Storage Adapter”


Here you can choose any other object type but you will have to choose the metric for that object type as well. Now you can click on any Object Type and I selected “Flash Array Volume” as shown below.


Now you can expand any Attributes and select “Flash Array Volume” metrics. For example, I selected “Read Latency (us)”. My goal is to sum “Read Latency (us)”and “Write Latency (us)”  together, since we do not have that metric available to us. So I am going to make a Super Metric called “TotalLatency”.

Double Click on “Read Latency (us)” as shown below.


Now in the formula below (as shown in the picture below) you can change the depth to a higher number like 2 to include objects like Flash array host which are higher in hierarchical chain. Every time you increase the depth by 1 you are going to be able to traverse the underlying parent object in your environment.


Now you can close the parenthesis as shown below by clicking on “Operators” drop down menu and selecting “)”


Now select “+” from the Operators drop down menu as shown below to add “Write Latency (us)” just like we did for “Read Latency (us)”.


I have shown the picture below to describe after you add the sum(${adaptertype=PureStorageAdapter, objecttype=Volume, attribute=Performance|Microsec_Per_Write, depth=2})


Now, Give the Super Metric a Name like I gave “Average_Latency ”, and click on “save” below.average_latency2

Highlight the SuperMetric you just created by left clicking on the row which has the SuperMetric in it. I have highlighted the super metric below in blue below.


In the same page click on “Object Types” tab below and click on “+” sign. Now you will be adding various adapters on which this super metric will operate.


Select Flash Array Volume.


click on “Select” below.


You will see that “Flash Array Volume” object type has been added for this Super Metric.


Now in order to add another object type for this super metric you have to click on “+” under “Object Types”. Click on drop down menu and select “FlashArray Host” this time.


click on “FlashArray Host” as shown below.


Now you have added two object types “Flash Array Volumes” and “Flash Array Host” to operate on “Average_Latency” SuperMetric.


Now we have to enable this SuperMetric “Average_Latency” in our default policy.

Click on Administration -> Policies. Then click on Policy Library tab as shown below.


Select Default Policy as shown below. I am choosing this Policy since this is the policy which I am using on all objects.


Click on Edit icon as shown below.


Click on “Collect Metrics and Properties” as shown below.


Click on “Attribute Type” as shown below.


Make sure to uncheck the Metric and Property boxes, under Attribute Type so you can only see the “SuperMetric”. This would make it easier to see the SuperMetric only.


Highlight all the SuperMetrics with “Average_Latency” and select all of them as shown below.


Click on “Actions” and then hover on “State” and select “Enable”. This will enable all the selected SuperMetrics with “Average_Latency”.


Now go to Environment -> FlashArray Resources as shown below.


Click on “PureStorage World”


Click on “FlashArray Volume” as shown below.


Click on any Volume like I clicked on “”.


Click on “TroubleShooting” Tab.


Click on “All Metrics” as shown below.


Click on “SuperMetrics” as shown below.


Double Click on “Average_Latency” or the SuperMetric you just created as shown below.


Now you have your SuperMetric created.