Notifications Node in Essentials
Applies To: System Center Essentials 2010
Notifications are messages that are automatically sent when an alert occurs on a monitored system. To configure a notification in Essentials 2010, you must first choose the format of the notification, then define what information the notification should contain, and finally define who should get the notifications. Each of these definitions must be completed in this order.
Choosing the format of the notification is called enabling a notification channel. The available notifications channels are command, e-mail, text messaging, and instant messaging. A command channel can run a script or executable file. After enabling the notification channel, you must then create at least one notification subscriber. You can then create a notification subscription, which defines when and from what device notifications can be sent, to whom they should be sent, and through which channels they should be sent. You can limit who receives notifications by group membership, object types, alert criteria such as severity, priority, resolution state, and even category of alert, and you can configure alert aging.
To send notifications, Essentials 2010 uses a variety of channels, such as command, e-mail, text messaging, and instant messaging. The length and format of the message varies based on the media that receives the notification.
The protocols supported by Essentials 2010 notification can work with a variety of e-mail, instant messaging, and text messaging systems. Essentials 2010 supports sending e-mail through Simple Mail Transfer Protocol (SMTP), as well as Session Initiation Protocol (SIP) and short message service (SMS), which supports the transmission of short text messages to and from mobile phones.
In addition, you can configure a notification to run a command instead of or in addition to sending a notification message. A command can specify a path to an application or script that can perform basic troubleshooting functions for a particular failure.
Notification Message Content
Essentials 2010 administrators can configure message content and length for a notification. Essentials 2010 has two default message formats: short and verbose. The default short format has only a subject and is designed for small bandwidth channels and devices, such as instant messages and pagers. The default verbose format has a subject and a message body and is designed for notification channels that have more bandwidth available, such as e-mail.
Essentials 2010 uses variables to define the subject and body content of a notification message. An example of a variable is $Alert Name$. This variable is replaced with the name of the alert that triggered the notification. An administrator can accept the defaults for the short and verbose messages or edit the subject and content of a notification message.
Administrators can set a schedule to rotate which subscriber receives a notification message. Also, Essentials 2010 can accommodate different notification channels and endpoints with a variety of delivery protocols and formats. For example, some operators prefer to receive notifications on a pager, while others might prefer to receive notifications by e-mail.
A subscriber is the user that receives the notification message. In Essentials 2010, you can define subscribers by list or by group membership.
Compiling a list manually is the most straightforward way to define notification subscriber. Use this approach if the list of recipients does not change. For a less labor-intensive method, use group membership. If you are using Essentials 2010 in an Active Directory network environment, you can use group membership to determine who receives notification messages. Additionally, Active Directory accounts can store all contact information, including e-mail addresses, telephone numbers, and pager information. With Active Directory integration, Essentials 2010 is automatically informed of any change to the contact information of an account.