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
agent.logLevel.SystemOut
This property redirects System.out to agent.log. Commenting out this seing causes System.out to be
directed to agent.log.startup.
The default value is INFO.
Configuring the Debug Level for an Agent Subsystem
For troubleshooting purposes, you can increase the logging level for an individual agent subsystem.
To increase the logging level for an individual agent subsystem, uncomment the appropriate line in the
section of the agent.properties le that is labelled Agent Subsystems: Uncomment individual subsystems
to see debug messages.
Agent log4j Properties
This is the log4j properties in the agent.properties le.
log4j.rootLogger=${agent.logLevel}, R
log4j.appender.R.File=${agent.logFile}
log4j.appender.R.MaxBackupIndex=1
log4j.appender.R.MaxFileSize=5000KB
log4j.appender.R.layout.ConversionPattern=%d{dd-MM-yyyy HH:mm:ss,SSS z} %-5p [%t] [%c{1}@%L] %m%n
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R=org.apache.log4j.RollingFileAppender
##
## Disable overly verbose logging
##
log4j.logger.org.apache.http=ERROR
log4j.logger.org.springframework.web.client.RestTemplate=ERROR
log4j.logger.org.hyperic.hq.measurement.agent.server.SenderThread=INFO
log4j.logger.org.hyperic.hq.agent.server.AgentDListProvider=INFO
log4j.logger.org.hyperic.hq.agent.server.MeasurementSchedule=INFO
log4j.logger.org.hyperic.util.units=INFO
log4j.logger.org.hyperic.hq.product.pluginxml=INFO
# Only log errors from naming context
log4j.category.org.jnp.interfaces.NamingContext=ERROR
log4j.category.org.apache.axis=ERROR
#Agent Subsystems: Uncomment individual subsystems to see debug messages.
#-----------------------------------------------------------------------
#log4j.logger.org.hyperic.hq.autoinventory=DEBUG
#log4j.logger.org.hyperic.hq.livedata=DEBUG
#log4j.logger.org.hyperic.hq.measurement=DEBUG
#log4j.logger.org.hyperic.hq.control=DEBUG
#Agent Plugin Implementations
#log4j.logger.org.hyperic.hq.product=DEBUG
#Server Communication
#log4j.logger.org.hyperic.hq.bizapp.client.AgentCallbackClient=DEBUG
#Server Realtime commands dispatcher
#log4j.logger.org.hyperic.hq.agent.server.CommandDispatcher=DEBUG
Chapter 3 Customizing How vRealize Operations Manager Monitors Your Environment
VMware, Inc. 125