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
Property Symptoms
Property symptoms are based on the conguration properties that vRealize Operations Manager collects
from the target objects in your environment.
You dene symptoms based on properties so that you can create alert denitions that let you know when
changes to properties on your monitored objects can aect the behavior of the objects in your environment.
Message Event Symptoms
Message event symptoms are based on events received as messages from a component of
vRealize Operations Manager or from an external monitored system through the system's REST API. You
dene symptoms based on message events to include in alert denitions that use these symptoms. When the
congured symptom condition is true, the symptom is triggered.
The adapters for the external monitored systems and the REST API are inbound channels for collecting
events from external sources. Adapters and the REST server both run in the vRealize Operations Manager
system. The external system sends the messages, and vRealize Operations Manager collects them.
You can create message event symptoms for the supported event types. The following list is of supported
event types with example events.
n
System Performance Degradation. This message event type corresponds to the
EVENT_CLASS_SYSTEM and EVENT_SUBCLASS_PERFORM_DEGRADATION type and subtype in
the vRealize Operations Manager API SDK.
n
Change. The VMware adapter sends a change event when the CPU limit for a virtual machine is
changed from unlimited to 2 GHz. You can create a symptom to detect CPU contention issues as a
result of this conguration change. This message event type corresponds to the
EVENT_CLASS_CHANGE and EVENT_SUBCLASS_CHANGE type and subtype in the
vRealize Operations Manager API SDK.
n
Environment Down. The vRealize Operations Manager adapter sends an environment down event
when the collector component is not communicating with the other components. You can create a
symptom that is used for internal health monitoring. This message event type corresponds to the
EVENT_CLASS_ENVIRONMENT and EVENT_SUBCLASS_DOWN type and subtype in the
vRealize Operations Manager API SDK.
n
Notication. This message event type corresponds to the EVENT_CLASS_NOTIFICATION and
EVENT_SUBCLASS_EXTEVENT type and subtype in the vRealize Operations Manager API SDK.
Fault Symptoms
Fault symptoms are based on events published by monitored systems. vRealize Operations Manager
correlates a subset of these events and delivers them as faults. Faults are intended to signify events in the
monitored systems that aect the availability of objects in your environment. You dene symptoms based
on faults to include in alert denitions that use these symptoms. When the congured symptom condition is
true, the symptom is triggered.
You can create fault symptoms for the supported published faults. Some object types have multiple fault
denitions from which to choose, while others have no fault denitions.
If the adapter published fault denitions for an object type, you can select one or more fault events for a
given fault while you dene the symptom. The symptom is triggered if the fault is active because of any of
the chosen events. If you do not select a fault event, the symptom is triggered if the fault is active because of
a fault event.
vRealize Operations Manager Customization and Administration Guide
60 VMware, Inc.