5.6

<condition type="Level">Critical</condition>
</Conditions>
<Addresses>
<sendTo type="email">[e-mail]</sendTo>
<sendTo type="sms">[e-mail] </sendTo>
</Addresses>
</FilterRule>
<FilterRule name="ResourceKindAlerts">
<Conditions>
<condition type="ResourceKind">OPEN_API:DEMO</condition>
<condition type="Status">New</condition>
<condition type="Tag">Location:NewYork</condition>
</Conditions>
<Addresses>
<sendTo type="email">[e-mail]</sendTo>
<sendTo type="sms">[e-mail]</sendTo>
</Addresses>
</FilterRule>
</EmailFilter>
<Templates> Element
The first part of the emailFilter.xml file is a <Templates> element, which contains a series of <Template>
elements. Each element specifies the template file to use for alert email messages of a particular type, subtype,
and status. You can use the following types of template files.
Default templates
Default template files, which are included with vCenter Operations Manager,
are designed to use with an alert type, subtype, and status if a custom file is
not specified for the recipient. emailFilter.xml includes a <template> element
for each default template. Do not change these elements. To change the
messages sent to all users for a particular alert type, modify the default message
template.
Custom templates
Custom template files are unique to your installation and are designed for
particular users. The <template> element for a custom template includes a
<sendTo> attribute that specifies the recipient.
The following sample element is a default template.
<Template alert_type="ADMINISTRATIVE" alert_subtype="ENVIRONMENT" status="NEW">
New-Administrative-Environment.html</Template>
The following sample element is a custom template.
<Template sendTo="[e-mail]" alert_type="ADMINISTRATIVE" alert_subtype="ENVIRONMENT"
status="NEW">abc-New-Administrative-Environment.html</Template>
Chapter 7 Configuring Alert Notifications
VMware, Inc. 93