![\"subscribe-and-save\"](\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2017\/04\/subscribe-and-save.png\")
<\/p>\n<\/p>\n
<\/p>\n
Let’s talk notifications for a minute.<\/p>\n
Everyone complains that a tool is noisy for alerts (typically emails).<\/p>\n
Why not find a way to limit what you receive, and eliminate, the noise.<\/p>\n
Sure, there’s alert tuning, but there are a ton of built-in options with Subscriptions in SCOM.<\/p>\n
<\/p>\n
![\"howto\"](\"https:\/\/kevinjustin.com\/blog\/wp-content\/uploads\/2017\/04\/HowTo.jpg\")
<\/p>\n
Let’s Start by talking about now a subscription is built in SCOM.<\/p>\n
Step 1 – An owner (or ‘subscriber’) is needed<\/p>\n
This can be an email address, group name or variable you may want to pass to a command line for a destination (e.g. support team\/NOC\/POC)<\/p>\n
Step 2 – A channel is needed (simply put, a way to get the data out of SCOM)<\/p>\n
This can be SMTP (email), or a custom executable to a ticketing system, NetCool, BMC True Sight, xMatters, Derdack, to name a few.<\/p>\n
Step 3 – Criteria to send to an owner (details)<\/p>\n
Do you have the necessary 3 parts (subscriber, channel)<\/p>\n
Do you have a destination\/subscriber already set up?<\/p>\n
Yes, see go to Channel<\/p>\n
No, follow the subscriber blog here<\/p>\n
Do you have a channel set up<\/p>\n
Yes, see go to Subscription<\/p>\n
No, follow the Channel\u00a0blog here<\/p>\n
<\/p>\n
Do you have a naming convention for the subscription parts?<\/p>\n
The Subscription name needs to be intuitive, i.e. Application Name, Team Name, Company Name (depending on the environment)<\/p>\n
Process an\u00a0Application’s alerts<\/p>\n
Example<\/strong>\u00a0\u00a0\u00a0\u00a0 ‘BizTalk alerts’<\/p>\n If BizTalk alerts needed to go to different teams<\/p>\n ‘BizTalk DEV Alerts’ or ‘BizTalk PROD Alerts’<\/p>\n or if Criteria is involved ‘BizTalk Performance Alerts’<\/p>\n or if alerts need to route to another company ‘Contoso BizTalk alerts’<\/p>\n Capitalize what needs emphasis so in the Subscriptions view (make searches or sorts easier and more intuitive)<\/p>\n Making sense where I’m going with this?<\/p>\n <\/p>\n Criteria can influence the name<\/p>\n CLASS, MONITOR, RULE, SEVERITY, GROUP, RESOLUTION STATE<\/p>\n To me the value comes in with the Description field in a subscription.<\/p>\n Adding relevant detail here makes life easier when followed, to know what the subscription is doing.<\/p>\n Try this model for the Subscription Description<\/p>\n CRITERIA<\/p>\n SUBSCRIBER<\/p>\n COMMENTS<\/p>\n