6.3
Table Of Contents
- vRealize Operations Manager Customization and Administration Guide
- Contents
- About Customization and Administration
- Configuring Users and Groups
- Customizing How vRealize Operations Manager Displays Your Data
- Customizing How vRealize Operations Manager Monitors Your Environment
- Defining Alerts in vRealize Operations Manager
- Object Relationship Hierarchies for Alert Definitions
- Alert Definition Best Practices
- Understanding Negative Symptoms for Alerts
- Create an Alert Definition for Department Objects
- Add Description and Base Object to Alert Definition
- Add a Virtual Machine CPU Usage Symptom to the Alert Definition
- Add a Host Memory Usage Symptom to the Alert Definition
- Add Recommendations to the Alert Definition
- Create a Custom Accounting Department Group
- Create a Policy for the Accounting Alert
- Configure Notifications for the Department Alert
- Create a Dashboard to Monitor Department Objects
- Defining Symptoms for Alerts
- Viewing Actions
- Defining Recommendations for Alert Definitions
- Creating and Managing Alert Notifications
- List of Outbound Plug-Ins
- Add Outbound Notification Plug-Ins
- Add a Standard Email Plug-In for Outbound Alerts
- Add a REST Plug-In for Outbound Alerts
- Add a Log File Plug-In for Outbound Alerts
- Add a Network Share Plug-In for vRealize Operations Manager Reports
- Add an SNMP Trap Plug-In for Outbound Alerts
- Add a Smarts Service Assurance Manager Notification Plug-In for Outbound Alerts
- Filtering Log File Outbound Messages With the TextFilter.xml File
- Configuring Notifications
- Defining Compliance Standards
- Operational Policies
- Managing and Administering Policies for vRealize Operations Manager
- Policy Decisions and Objectives
- Default Policy in vRealize Operations Manager
- Custom Policies
- Policies Provided with vRealize Operations Manager
- User Scenario: Create a Custom Operational Policy for a vSphere Production Environment
- User Scenario: Create an Operational Policy for Production vCenter Server Datastore Objects
- Create a Group Type for Your Datastore Objects
- Create an Object Group for Your Datastore Objects
- Create Your Policy and Select a Base Policy
- Override the Analysis Settings for the Datastore Objects
- Enable Disk Space Attributes for Datastore Objects
- Override Alert and Symptom Definitions for Datastore Objects
- Apply Your Datastore Policy to Your Datastore Objects Group
- Create a Dashboard for Disk Use of Your Datastore Objects
- Using the Monitoring Policy Workspace to Create and Modify Operational Policies
- Policy Workspace in vRealize Operations Manager
- Super Metrics in vRealize Operations Manager
- Customizing Icons
- Managing Objects in Your Environment
- Configuring Object Relationships
- Customizing How Endpoint Operations Management Monitors Operating Systems
- Modifying Global Settings
- Defining Alerts in vRealize Operations Manager
- Maintaining and Expanding vRealize Operations Manager
- Cluster and Node Maintenance
- Logging
- Passwords and Certificates
- How To Preserve Customized Content
- Backup and Restore
- OPS-CLI Command-Line Tool
- Index
Super Metrics in vRealize Operations Manager
The super metric is a mathematical formula that contains one or more metrics. It is a custom metric that you
design and is useful when you need to track combinations of metrics, either from a single object or from
multiple objects. If a single metric cannot tell you what you need to know about the behavior of your
environment, you can dene a super metric.
After you dene it, you assign the super metric to one or more object types. This action calculates the super
metric for the objects in that object type and simplies the metrics display. For example, if you dene a super
metric that calculates the average CPU usage on all virtual machines, and you assign the super metric to a
cluster, the average CPU usage on all virtual machines in that cluster is reported as a super metric for the
cluster.
When the super metric aribute is enabled in a policy, you can also collect super metrics from a group of
objects associated with a policy.
Super Metric Functions
vRealize Operations Manager includes functions that you can use in super metric formulas. The functions
are either looping functions or single functions.
Looping Functions
Looping functions work on more than one value.
Table 3‑6. Looping Functions
Function Description
avg Average of the collected values.
combine Combines all of the values of the metrics of the included
objects in a single metric timeline.
count Number of values collected.
max Maximum value of the collected values.
min Minimum value of the collected values.
sum Total of the collected values.
Looping Function Arguments
The looping function returns an aribute or metric value for an object or object type. An aribute is
metadata that describes the metric for the adapter to collect from the object. A metric is an instance of an
aribute. The argument syntax denes the desired result.
For example, CPU usage is an aribute of a virtual machine object. If a virtual machine has multiple CPUs,
the CPU usage for each CPU is a metric instance. If a virtual machine has one CPU, then the function for the
aribute or the metric return the same result.
Table 3‑7. Looping Function Formats
Argument syntax example Description
funct(${this, metric =a|b:optional_instance|c}) Returns a single data point of a particular metric for the object to
which the super metric is assigned. This super metric does not take
values from the children or parents of the object.
funct(${this, aribute=a|b:optional_instance|c}) Returns a set of data points for aributes of the object to which the
super metric is assigned. This super metric does not take values
from the child or parent of the object.
Chapter 3 Customizing How vRealize Operations Manager Monitors Your Environment
VMware, Inc. 103