5.7
Table Of Contents
- VMware vCenter Operations Manager Administration Guide
- Contents
- VMware vCenter Operations Manager Administration Guide
- Configuring and Managing vCenter Operations Manager
- Configuring Adapters
- Configuring Resources
- Configuring Attribute Packages
- Configuring Applications
- Configuring and Managing Users
- Configuring Alert Notifications
- Performing Basic System Administration Tasks
- View Performance Information
- View Status Information
- vCenter Operations Manager Service Names
- Start or Stop vCenter Operations Manager Services
- Viewing and Managing System Log Files
- Delete Old Data in the File System Database
- Run the Audit Report
- Modify Global Settings
- Modify Global Settings for Virtual Environments
- Create a Support Bundle
- Resolving Administrative System Alerts
- Analytics FSDB Overloaded
- Analytics Threshold Checking Overloaded
- Collector Is Down
- Controller Is Unable to Connect to MQ
- DataQueue Is Filling Up
- Describe Failed
- Failed to Connect to Replication MQ
- Failed to Repair Corrupted FSDB Files
- File Queue Is Full
- FSDB Files Corrupted for Resources
- FSDB Storage Drive Free Space Is Less Than 10%
- No DT Processors Connected
- One or More Resources Were Not Started
- Outbound Alert Send Failed
- Replication MQ Sender Is Blocked
- Backing Up and Recovering Data
- Backing Up and Recovering Data Components
- Backing Up and Recovering Processing Components
- Configuring the Repository Adapter
- Repository Adapter Requirements and Limitations
- Repository Adapter Configuration Steps
- Creating a Database User for the Repository Adapter
- Configure the Source Database Connection for the Repository Adapter
- Configure the Output Destination for the Repository Adapter
- Configuring the Source and Destination Columns for the Repository Adapter
- Configure Data Export Values for the Repository Adapter
- Customizing Repository Adapter Operation
- Start the Repository Adapter
- Using System Tools
- Using the Database Command Line Interface
- Index
Table 7-2. Elements for General Options
Element Description
<SendFromEmail> (Optional) Sets the address to use as the from address for all email alert
notifications. If you do not include this element,
vCenter Operations Manager sends messages from the default email sender
address in the
vcenter-ops
\user\conf\email.properties
configuration file.
<FilterRule> Element
The rest of the emailFilter.xml file contains one or more <FilterRule> elements. Each <FilterRule> element
defines a set of conditions for an alert and one or more email addresses to which to send notifications for all
alerts that meet those conditions. <FilterRule> should have a name attribute. The name attribute can be any
text that describes the filter rule.
Each <FilterRule> has one or more conditions, which are contained in a <Conditions> tag. Each <condition>
element includes a type setting and a value to match. In the sample file, the following conditions are used in
the first rule:
<Conditions>
<condition type="Application">Online Trading</condition>
<condition type="Tier">Online Trading:Web</condition>
<condition type=Level">Critical</condition>
</Conditions>
In this example, the rule contains three conditions. The first condition is of type Application and it checks for
the value Online Trading. The type setting defines the type of data to check for the matching value to determine
if the condition is met.
Table 7-3. Valid Type Settings
Type Description
AlertType Type of alert. For a list of alert types, see Table 7-1.
For example: <condition type="AlertType">ADMINISTRATIVE</condition>
AlertSubType Subtype of the alert. For the subtypes that you can use with each alert type, see Table 7-1.
For example: <condition type="AlertSubType">ENVIRONMENT</condition>
Application Name of a vCenter Operations Manager application. The condition matches if the alert is
for any resource in the application.
For example: <condition type="Application">OnlineTrading</condition>
Collector Unique name of a vCenter Operations Manager collector.
For example: <condition type="Collector">vCenter Operations
Collector</condition>
Level Minimum alert criticality level. Alerts of this level or above match this condition. Valid types
are NONE, INFO, WARNING, IMMEDIATE, and CRITICAL.
For example: <condition type="Level">immediate</condition>
ResourceKind Name of a resource kind in the format AdapterKind:ResourceKind.
For example: <condition type="ResourceKind">OPEN_API:DEMO</condition>
RootCauseTier Tier in an application. It is a match if one of the root causes of the alert is on the tier. You
must include the application name and the tier name in the format Application:Tier.
For example: <condition type="RootCauseTier">Online
Trading:Network</condition>
State State of the alert. Valid values are OPEN, ASSIGNED, SUSPENDED, and SUPPRESSED.
For example: <condition type="State">Open</condition>
Chapter 7 Configuring Alert Notifications
VMware, Inc. 85