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
plugins.include
Use this property to specify the plug-ins that the Endpoint Operations Management agent must load at
startup.
You supply a comma-separated list of plugins to include. For example, plugins.include=weblogic,apache.
Understanding the Unsynchronized Agents Group
An unsynchronized agent is an agent that is not synchronized with the vRealize Operations Manager server
in terms of its plug-ins. The agent might be missing plug-ins that are registered on the server, include plug-
ins that are not registered on the server, or include plug-ins that have a dierent version to that registered
on the server.
Each agent must be synchronized with the vRealize Operations Manager server. During the time that an
agent is not synchronized with the server, it appears in the Unsynchronized Agents list. The list is located in
the vRealize Operations Manager user interface on the Groups tab in the Environment view.
The rst time an agent is started, a status message is sent to the server. The server compares the status sent
by the agent with that on the server. The server sends commands to the agent to synchronize, download or
delete plug-ins, as required by the dierences that it detects.
When a plug-in is deployed, disabled, or enabled as part of a management pack solution update, the
vRealize Operations Manager server detects that change and sends a new command to the agents so that
synchronization occurs.
Commonly, multiple agents are aected at the same time when a plug-in is deployed, disabled or enabled.
All agents have an equal need to be updated so, to avoid overloading the server and creating performance
issues that might occur if many agents were all synchronized at the same time, synchronization is
performed in batches and is staggered in one-minute periods. You will notice that the list of unsynchronized
agents decrements over time.
Configuring Agent Logging
You can congure the name, location, and logging level for Endpoint Operations Management agent logs.
You can also redirect system messages to the agent log, and congure the debug log level for an agent
subsystem.
Agent Log Files
The Endpoint Operations Management agent log les are stored in the AgentHome/log directory.
Agent log les include the following:
agent.log
agent.operations.log
This log is applicable to Windows-based agents only.
This is an audit log that records the commands that were run on the agent,
together with the parameters that the agent used to action them.
wrapper.log
The Java service wrapper-based agent launcher writes messages to the
wrapper.log le. For a non-JRE agent, this le is located in
agentHome/wrapper/sbin.
In the event that the value was changed ifr the agent.logDir property, the le
is also located in agentHome/wrapper/sbin.
Chapter 3 Customizing How vRealize Operations Manager Monitors Your Environment
VMware, Inc. 123