Notification rules determine which alerts are sent to the target systems. You configure one or more notification rules to limit the data that vRealize Operations sends to systems or recipients.
How Notification Rules Work
Notification rules are filters that limit the data sent to external systems by using outbound alert plug-ins that are supported, configured, and running. Rather than sending all alerts to all your email recipients, you can use notification rules to send specific alerts. For example, you can send health alerts for virtual machines to one or more of your network operations engineers. You can send critical alerts for selected hosts and clusters to the virtual infrastructure administrator for those objects.
Before you can create and manage notification rules, you must configure the outbound alert plug-in instances.
You can configure one filtering selection, or you can configure as many selections as you need so that vRealize Operations sends only the required data to the target external system.
Where You Find Notification Rules
- Add the following notification details.
Option Description Name Name of the rule that you use to manage the rule instance. Description Description of the rule. Notification Status Either enable or disable a notification setting. Disabling a notification will stop the alert notification for that setting and enabling it will activate it again. - Click Next.
- Define criteria for the notification rule.
Option Description Object Scope Criteria Object Type, Object, Tags, Applications, and Tiers for which you are filtering the alert notifications.
After you select the type, you select the specific instance. For example, if you select Object, you then select the specific object by name and determine whether to include any child objects.
Alert Scope Category Alert Types/Subtypes, Alert Impact, or Alert Definition that triggers the alert.
After you select the criteria, you can configure the specific selections associated with the criteria. For example, if you select Alert Definition, you then select the alert definition that limits the data to alerts with this definition. You can select multiple alert definitions as conditions for a notification to trigger.
Criticality Defined criticality of the alert that results in the data being sent to an external system. For example, if you select Critical, then the data that is sent to the external system must also be labeled as critical.
Control State State of the alert, either opened, assigned, or suspended. Notify On Status Current state of the alert, either canceled, updated, or new.
Advanced Filters: By Collector Collector/Group Select a collector or group if you want to receive notifications for the objects which receive data from the selected collector/group.
Note: If you do not define any alert filters in the Define Criteria tab, then the notification will be sent for all the alerts without applying any conditions for the object scope, alert scope, or alert state. - Click Next.
- Select the outbound method that you want to use to send your notification.
Option Description Outbound Method -
Select Plug-In Type: Type of plugin. Select one of the outbound alert plug-in types: Log File Plugin, Rest Notification Plugin, Standard Email Plugin, SNMP Trap Plugin, Webhook Notification Plugin, Slack Plugin, and Service-Now Notification Plugin.Note: The Rest Notification Plugin is deprecated in this release. Although you still can configure the Rest Notification Plugin, you will not be able to use a custom template for it. You can use the Webhook Notification Plugin instead of the Rest Notification Plugin.
- Select Instance: Select the configured instance for the type of plug-in.
- Create New Instance: You can also create a new outbound instance for the plug-in type you select.
For details, see Add Outbound Notification Plug-Ins in vRealize Operations.
-
- Click Next.
- Select the payload template.
Option Description Payload Template Select the payload template that you want to include in the notification. Each plug-in has its default template and you can select the default template if no customization is required. The template includes additional information about the alert or the object that is displayed in the notification. You can also customize your payload for a Webhook Notification Plugin. For details on creating payload templates, see Create a Payload Template. The values in this tab differ based on the outbound plug-in you have selected in the previous step. Outbound Method -Standard Email Plugin If you are configuring notifications for standard email, you can add recipients and associated information.
- Recipient(s). Enter the email addresses of the individuals to whom you are sending email messages that contain alert notifications. If you are sending to more than one recipient, use a semicolon (;) between addresses.
- Cc Recipients. Enter the emails addresses of the individuals that have to be cc'd for the email.
- Bcc Recipients. Enter the emails addresses of the individuals that have to be bcc'd for the email.
- Notify again. Number of minutes between notifications messages for active alerts. Leave the text box empty to send only one message per alert.
- Max Notifications. Number of times to send the notification for the active alert. Leave the text box empty to send only one message per alert.
- Delay to notify. Number of minutes to delay before sending a notification when a new alert is generated. For example, if the delay is 10 minutes and a new alert is generated, the notification is not sent for 10 minutes. If the alert is canceled in those 10 minutes, the notification is not sent. The notification delay reduces the number of notifications for alerts that are canceled during that time.
- Description. Enter the text to include in the email message. For example, Attention Host Management team.
Outbound Method - Service-Now Notification Plugin If you are configuring notifications for a Service-Now notification plug-in, you can add instances and associated information. - Caller. Enter the name of the person who reported the incident or who is affected by the incident.
- Category. Specify the category to which the incident belongs.
- Sub Category. Specify the sub category to which the incident belongs.
- Business Service. Specify the business service of the incident.
- Contact Type. Enter the contact type.
- State. Enter the incident state in digits.
- Resolution Code. Enter the resolution code for the incident.
- Resolution notes. Enter the resolution notes for the incident.
- On hold reason. Enter the reason as to why the incident is on hold.
- Impact. Set the incident impact in digits. Impact measures the business criticality of the affected service.
- Urgency. Set urgency for the incident in digits. Urgency defines the number of days taken to resolve an incident.
- Priority. Enter the priority for the incident. Priority defines the sequence in which the incident must be resolved.
- Assignment Group. Enter the assignment group for the incident.
- Assigned To. Enter the details of the person to whom the incident is assigned.
- Severity. Set the severity for the incident in digits.
- Upon Approval. Specify the next steps to be taken upon incident approval.
- Problem. Enter the details of the related problem if it exists.
- Cause by change. Enter the change request which triggered the incident.
- Change Request. Enter the details for the related change list if it exists.
Outbound Method - Slack Plugin If you are configuring notifications for a Slack plugin, add the Webhook URL of Slack. For example, the Webhook URL is in the format: https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX. Create and authorize an app within Slack to obtain the Webhook URL. For details on creating and authorizing an app within Slack, refer to the Slack Documentation.
Once you have created the notification rule, the alerts are displayed within that particular Slack channel with a link to the alert. Click the link to view the details of the alert in the Object Summary page.
- Click Create to create the notification rule. You can view the rule you created under .
