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
c From the Alert Type and Subtype drop-down menu, expand Virtualization/Hypervisor and select
Compliance.
Any alert where you use the Compliance subtype is processed as a compliance standard.
d Congure the Wait Cycle and Cancel Cycle with a value of 1.
What to do next
Add the symptoms that act as the compliance rules. See “Add Symptoms to the Host Compliance Standard,”
on page 79.
Add Symptoms to the Host Compliance Standard
You add symptoms and recommendations to the alert denition so that when the host system compliance
alert is generated, the symptoms appear as rules on the Compliance tab.
Prerequisites
Congure the name, host object type, and alert impact seing for the alert so that it appears as a compliance
standard. See “Congure Basic Information for the Host Compliance Standard,” on page 78.
Procedure
1 In the Alert Denition Workspace window, click Add Symptom and add the SSH
symptom.
a From the Symptom Type drop-down menu, select Metric / Property.
b In the Symptom search text box, enter SSH.
c Drag the symptom named SSH service is running to the symptoms workspace.
If you add multiple symptoms for your own scenario, and you determine that the alert must trigger
when any of the symptoms occur, you would select Any from the drop-down menu named This
symptom set is true when.
2 In the workspace navigation pane, click Add Recommendations, and create a recommendation for the
standard.
a Click the plus sign to add a recommendation.
b Enter a name for the recommendation in the text box.
For example, enter Turn on the SSH service. If you have a local runbook, you can provide a link to
your local instructions.
c Click Save.
d Drag the recommendation to the workspace.
In your own scenario, you can create multiple recommendations for the standard.
3 Click Save.
If the symptom condition becomes true, the symptom is triggered and the compliance alert is generated for
the object. Because the alert denition includes the subtype named Compliance, the generated alert appears
as a compliance standard on the Compliance tab.
What to do next
Review the Compliance tab for standards that indicate that other objects are out of compliance, including
vCenter Server instances, virtual machines, distributed port groups, and distributed switches. See the
vRealize Operations Manager User Guide.
Chapter 3 Customizing How vRealize Operations Manager Monitors Your Environment
VMware, Inc. 79