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
List of Global Settings
The global seings determine how vRealize Operations Manager retains data, keeps connection sessions
open, and other seings. These are system seings that aect all users.
Table 3‑27. Global Setting Default Values and Descriptions
Setting
Default
Value Description
Action History 90 days Number of days to retain the recent task data for actions.
The data is purged from the system after the specied number
of days.
Deleted Objects 360 hours Number of hours to retain objects that are deleted from an
adapter data source or server before deleting them from
vRealize Operations Manager.
An object deleted from an adapter data source might be
identied by vRealize Operations Manager as not existing and
vRealize Operations Manager can no longer collect data about
the object. Whether vRealize Operations Manager identies
deleted objects as not existing depends the adapter. This feature
is not implemented in some adapters.
For example, if the retention time is 360 hour and a virtual
machine is deleted from a vCenter Server instance, the virtual
machine remains as an object in vRealize Operations Manager
for 15 days before it is deleted.
This seing applies to objects deleted from the data source or
server, not to any objects you delete from
vRealize Operations Manager on the Inventory Explorer page.
A value of -1 deletes objects immediately.
Deletion Schedule Interval 24 hours Determines the frequency to schedule deletion of resources.
This seing works with the Deleted Objects seing to remove
objects that no longer exist in the environment.
vRealize Operations Manager transparently marks objects for
removal that have not existed for the length of time specied
under Deleted Objects. vRealize Operations Manager then
removes the marked objects at the frequency specied under
Deletion Scheduling Interval.
Object History 300 days Number of days to retain the history of the object conguration,
relationship, and property data.
The conguration data is the collected data from the monitored
objects on which the metrics are based. The collected data
includes changes to the conguration of the object.
The data is purged from the system after the specied number
of days.
Session Timeout 30 minutes If your connection to vRealize Operations Manager is idle for
the specied amount of time, you are logged out of the
application.
You must provide credentials to log back in.
Symptoms/Alerts 90 days Number of days to retain canceled alerts and symptoms.
The alerts and symptoms can be canceled by the system or
canceled by a user.
Time Series Data 6 months Number of months that you want to retain the collected and
calculated metric data for the monitored objects.
If available disk space is less than 10%,
vRealize Operations Manager purges older data and might not
retain the full range specied.
Chapter 3 Customizing How vRealize Operations Manager Monitors Your Environment
VMware, Inc. 127