Create a super metric when you want to check the health of your environment, but cannot find a suitable metric to perform the analysis.


  1. From the left menu, click Configure and then click Super Metrics.
  2. Click the Add icon.
    The Manage Super Metric wizard opens.
  3. Enter a meaningful name for the super metric such as Worst VM CPU Usage (%) in the Name text box.
    Note: It is important that you have an intuitive name as it appears in dashboards, alerts, and reports. For meaningful names, always use space between words so that it is easier to read. Use title case for consistency with the out of the box metrics and add the unit at the end.
  4. Provide a brief summary of the super metric in the Description text box.
    Note: Information regarding the super metric, like why it was created and by whom can provide clarity and help you track your super metrics with ease.
  5. Select the unit of the super metrics from the Unit drop-down and click Next.
    Note: The super metrics unit configured here can be changed in the metrics charts, widgets, and views.
    The Create a formula screen appears.
  6. Create the formula for the super metric.
    For example, to add a super metric that captures the average CPU usage across all virtual machines in a cluster, perform the following steps.
    1. Select the function or operator. This selection helps combine the metric expression with operators and/or functions. In the super metric editor, enter avg and select the avg function.
      You can manually enter functions, operators, objects, object types, metrics, metrics types, property, and properties types in the text box and use the suggestive text to complete your super metric formula.

      Alternatively, select the function or operator from the Functions and Operators drop-down menus.

    2. To create a metric expression, enter Virtual and select Virtual Machine from the object type list.
    3. Add the metric type, enter usage, and select the CPU|Usage (%) metric from the metric type list.
      Note: The expression ends with depth=1 by default. If the expression ends with depth=1, that means that the metric is assigned to an object that is one level above virtual machines in the relationship chain. However, since this super metric is for a cluster which is two levels above virtual machine in the relationship chain, change the depth to 2.

      The depth can also be negative, this happens when you need to aggregate the parents of a child object. For example, when aggregating all the VMs in a datastore, the metric expression ends with depth=-1, because VM is a parent object of datastore. But, if you want to aggregate all the VMs at a Datastore Cluster level, you need to implement 2 super metrics. You cannot directly aggregate from VM to Datastore Cluster, because both are parents of a datastore. For a super metric to be valid, depth cannot be 0 (-1+1=0). Hence, you need to create the first super metric (with depth=-1) for the aggregate at the datastore level, and then build the second super metric based on the first (with depth = 1).

      The metric expression is created.
    4. To calculate the average CPU usage of powered on virtual machines in a cluster, you can add the where clause. Enter where=””.
      Note: The where clause cannot point to another object, but can point to a different metric in the same object. For example, you cannot count the number of VMs in a cluster with the CPU contention metric > SLA of that cluster. The phrase "SLA of that cluster " belongs to the cluster object, and not to the VM object. The right operand must also be a number and cannot be another super metric or variable. The where clause cannot be combined using AND, OR, NOT, which means you cannot have where="VM CPU>4 and VM RAM>16" in your super metric formula.
    5. Position the pointer between the quotation marks, enter Virtual, and select the Virtual Machine object type and the System|Powered ON metric type.
    6. To add the numeric value for the metric, enter ==1.
    7. To view hints and suggestions, click ctrl+space and select the adapter type, objects, object types, metrics, metrics types, property, and properties types to build your super metric formula.
    8. Click the This object icon.

      If the This object icon is selected during the creation of a metric expression, it means that the metric expression is associated to the object for which the super metric is created.

  7. You can also use the Legacy template to create a super metric formula without the suggestive text.
    To view the super metric formula in a human-readable format, click the Show Formula Description icon. If the formula syntax is wrong, an error message appears.
    Note: If you are using Internet Explorer, you are automatically directed to the legacy template.
  8. Verify that the super metric formula has been created correctly.
    1. Expand the Preview section.
    2. In the Objects text box, enter and select a Cluster.
      A metric graph is displayed showing values of the metric collected for the object. Verify that the graph shows values over time.
    3. Click the Snapshots icon.
      You can save a snapshot, or download the metric chart in a .csv format.
    4. Click the Monitoring Objects icon.
      If enabled, only the objects that are being monitored are used in the formula calculation.
    5. Click Next.
    The Assign to Object Types screen appears.
  9. Associate the super metric with an object type. vRealize Operations Cloud calculates the super metric for the target objects and displays it as a metric for the object type.
    1. In the Assign to an Object Type text box, enter Cluster and select the Cluster Compute Resource object type.
      After one collection cycle, the super metric appears on each instance of the specified object type. For example, if you define a super metric to calculate the average CPU usage across all virtual machines and assign it to the cluster object type, the super metric appears as a super metric on each cluster.
    2. Click Next.
      The Enable in a Policy screen appears.
  10. Enable the super metric in a policy, wait for at least one collection cycle till the super metric begins collecting and processing data, and then review your super metric on the All Metrics tab.
    1. In the Enable in a Policy section, you can view the policies related to the object types you assigned your super metric to. Select the policy in which you want to enable the super metric. For example, select the Default Policy for Cluster.
  11. Click Finish.
    You can now view the super metric you created and the associated object type and policy on the Super Metrics page.