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
What to do next
Continue in the workspace, adding symptoms to your alert denition. See “Add a Virtual Machine CPU
Usage Symptom to the Alert Denition,” on page 51.
Add a Virtual Machine CPU Usage Symptom to the Alert Definition
To generate alerts related to CPU usage on your accounting virtual machines, you add symptoms to your
vRealize Operations Manager alert denition after you provide the basic descriptive information for the
alert. The rst symptom you add is related to CPU usage on virtual machines. You later use a policy and
group to apply alert to the accounting virtual machines.
This scenario has two symptoms, one for the accounting virtual machines and one to monitor the hosts on
which the virtual machines operate.
Prerequisites
Begin conguring the alert denition. See “Add Description and Base Object to Alert Denition,” on
page 50.
Procedure
1 In the Alert Denition Workspace window, after you congure the Name and Description, Base Object
Type, and Alert Impact, click Add Symptom and congure the symptoms.
2 Begin conguring the symptom set related to virtual machines CPU usage.
a From the On drop-down menu, select Child.
b From the Filter by Object Type drop-down menu, select Virtual Machine.
c From the Symptom Type drop-down menu, select Metric / Supermetric.
d Click the Add buon to open the Add Symptom Denition workspace window.
3 Congure the virtual machine CPU usage symptom in the Add Symptom Denition workspace
window.
a From the Base Object Type drop-down menu, expand vCenter Adapter and select Virtual
Machine.
The collected metrics for virtual machines appears in the list.
b In the metrics list Search text box, which searches the metric names, type usage.
c In the list, expand CPU and drag Usage (%) to the workspace on the right.
d From the threshold drop-down menu, select Dynamic Threshold.
Dynamic thresholds use vRealize Operations Manager analytics to identify the trend metric values
for objects.
e In the Symptom Name text box, type a name similar to VM CPU Usage above trend.
f From the criticality drop-down menu, select Warning.
g From the threshold drop-down menu, select Above Threshold.
h Leave the Wait Cycle and Cancel Cycle at the default values of 3.
This Wait Cycle seing requires the symptom condition to be true for 3 collection cycles before the
symptom is triggered. This wait avoids triggering the symptom when there is a short spike in CPU
usage.
i Click Save.
Chapter 3 Customizing How vRealize Operations Manager Monitors Your Environment
VMware, Inc. 51