If you want your subscribers to receive alert notifications for specific alerts over a given notification channel, then you'll need to configure a subscription to tie all of the notification components together.
The process of creating custom subscriptions is very similar to the wizard-driven process of creating rules in Microsoft Outlook to determine how e-mails are handled when they're received. Criteria conditions are specified within the subscription to determine if and when alerts will be sent to specific subscribers. Using the console, you can create a new custom subscription from scratch through the Administration workspace or you can create a targeted subscription direct from an alert within the Monitoring workspace.
When configuring new alert subscriptions, it's a good idea to plan the types of alerts that you wish to send to subscribers. For example, you might decide to only send alerts with a resolution state of New and a severity of Critical to operators working outside normal business hours. This type of subscription will ensure that the on-call team don't get woken up during the night for alerts that may not be too important and it will help to increase confidence in the monitoring solution for everyone involved in managing the IT estate.
To create a new subscription from the Administration workspace, follow these steps:
If you want to roll out your PowerShell Kung-Fu again, you can use the Add-SCOMNotificationSubscription
cmdlet to create new subscriptions. You can find all the syntax information and some sample scripts here - http://tinyurl.com/opsmgraddsubscription
An easy way of creating notification subscriptions for specific alerts is to open an alert view in the Monitoring workspace, right-click on the alert and select the Notification subscription option from the menu as shown in Figure 10.21.
The Create option from the menu launches the Notification Subscription Wizard and will pre-populate a name, description and the created by specific rules or monitors subscription criteria similar to Figure 10.22.
When creating scoped subscriptions from the Monitoring workspace, be aware that the default pre-populated criteria doesn't add a resolution state criteria. This means that you will be notified on all alerts – including those with a resolution state of Closed. This can generate unnecessary notification noise for your operators and it's a good idea to specify the New resolution state criteria here.
Subscribers and channels are not pre-populated when you create a scoped subscription so you'll need to add these as you work through the remaining steps in the wizard.
If you've already created some scoped alert notification subscriptions that target specific alerts, you can use the Modify option from the Notification subscription menu after you right-click on an alert in the console. Selecting this option will present you with the Select Subscription dialog box shown in Figure 10.23. Here, you can choose the subscription you wish to add the scoped alert notification to and as you select a subscription from the list, the informational description at the bottom will change to explain if your modification will broaden or restrict the overall scope of the original subscription.
18.222.35.77