Comments on: Using Resolution States to fine tune alert notifications

By: Steve Lee

Steve Lee — Tue, 14 Oct 2008 19:40:19 +0000

Thanks Jeremy. While I was teaching myself just enough PowerShell to get this done, I discovered mapping email addresses back to a resolution state with “switch” was a little much. Here’s the script I’m using now with small-scale success (most remarks removed):

#—-
$resState = 0
$RMS = “yourrmshere”

Add-PSSnapin “Microsoft.EnterpriseManagement.OperationsManager.Client”
Set-Location “OperationsManagerMonitoring::”
New-ManagementGroupConnection -ConnectionString:$RMS
Set-Location $RMS

$momapi = New-Object -comObject “MOM.ScriptAPI”

# Gather all the alerts in ‘new’ state and with CustomField 10 in the range required
$alerts = Get-Alert | Where-Object {$_.ResolutionState -eq 0 -and {$_.CustomField10 -gt 50 -and $_.CustomField10 -lt 200}}

# Now that we have our alerts, lets change the resolution state to equal the custom field.
foreach ($alert in $alerts) {
# Change resolution state
if ($alert.CustomField10 -gt 0 -and $alert.CustomField10 -lt 255)
{$alert.ResolutionState = $alert.CustomField10
# Update the RMS
$alert.Update(“”)}
}
#—-

I’ve created several custom resolution states, like 52=Messaging Team, 53=Applications Team, etc.. Any custom rules or monitors beyond the Exchange MP can have CustomField10 set to 52, then a subscription filtered for the “Messaging Team” resolution state delivers only those alerts to them. I think I can also use the severity flags to determine whether a subscription goes to pager, email, or just IM.

Thanks again for a great solution.

By: Jeremy D. Pavleck

Jeremy D. Pavleck — Tue, 14 Oct 2008 13:17:54 +0000

Hey Steve,
Using email addresses won’t work so well, as it’s not a simple matter to cause a notification to occur in response to an alert. A custom resolution state in a custom field would work well though – and a PS switch -match statement would be great.
In fact I have an expanded script that matches alert names based on a switch statement, and it does great as long as there aren’t a lot of alerts in the pipeline.

By: Steve Lee

Steve Lee — Mon, 13 Oct 2008 15:18:22 +0000

I’m thinking of a twist on this that uses either email addresses or just the customized resolution state value in a Custom Field. The script could grab the value in the Custom Field of your choice, and either change the resolution state to equal the Custom Field, or compare it to a lookup list (like a PS “switch” statement), then map the resolution state to a specific subscription.

Still trying to map it out in my head, and I’m not sure I know enough PowerShell to do it myself… Does this sound feasible?

By: Jeremy D. Pavleck

Jeremy D. Pavleck — Wed, 10 Sep 2008 20:24:12 +0000

bah! 5 mins, I’ll fix this.

By: Jeremy D. Pavleck

Jeremy D. Pavleck — Wed, 10 Sep 2008 20:22:42 +0000

Ethan,
If you look in the screenshot you can see what I mean, it’s the HTML code for &, which is

instead of &

By: Ethan Froese

Ethan Froese — Wed, 10 Sep 2008 20:00:39 +0000

What does the following mean in your instructions?

“Configure the command line execution settings as shown – remembering to use “&” instead of “&”.”

By: Jeremy D. Pavleck

Jeremy D. Pavleck — Wed, 10 Sep 2008 19:50:26 +0000

Hi John,
That’s a typo in the script regarding the resolution state. Should be $alert.ResolutionState = $resState, I’ll have to fix that. One of the problems of testing something then trying to just edit it so you can publish it.

I’m not quite understanding your question in your first post – except that the correction listed in the comments for #14 are correct, if you look at the screenshot you can see what I was trying to say. If you’re having further questions, contact me at jeremy at pavleck dot net

By: John Bradshaw

John Bradshaw — Wed, 10 Sep 2008 07:14:05 +0000

Hi,
Just one more Q….
Do the lines in the PS script have to agree in value (Below they both have a value of 10? So if I change the Alert Resolution state to 1, then both lines should be 1 in the script?
Thx
JB

$resState = 10 # Our custom resolution state

$alert.ResolutionState = 10

By: John Bradshaw

John Bradshaw — Wed, 10 Sep 2008 06:24:18 +0000

Hi,
Thx for this. Looks good.
I am still having trouble generating an e-mail alert from this. If I have a subscription to send an email on any windows 2003 server critical event, then I get an e-mail for this alert, but using the specific criterial listed above I receive no email alert, even though SCOM has registered the critical alert.
I did notice that someone queried a typo in Point 14 above. Is the line correct in the main body of the text above, or should it be amended?
Thx,
JB

By: System Center Forum - Tip: Four ways to target notifications to a more granular level OpsMgr and Essentials 2007

Tue, 09 Sep 2008 02:17:43 +0000

[...] As you will see, there’s a lot of flexibility in this method, although it takes some work. As Jeremy Pavleck mentions, you have 254 possible resolution states that can be used to in a Notification [...]