Hi there,

I would like to list all rules which create a critical alert with prio 1. When I use the get-rule cmdlet I can not see the severity property, so there is no way to make that selection that way. How could I get this done?

Pls help. Thanx in advance.

Regards,

Chris

>get-rule|where-object {$_.displayname -like "*An SQL job failed to complete success
fully*"}

ManagementGroup        : <MG>

ManagementGroupId      : <id>

HasNonCategoryOverride : True
Enabled                : false
Target                 : ManagementPackElementUniqueIdentifier=1d101d88-d885-4be6-7
                         ad2-fe27cba4b4bf
ConfirmDelivery        : True
Remotable              : True
Priority               : Normal
DiscardLevel           : 100
Category               : EventCollection
ConditionDetection     :
DataSourceCollection   : {_F6DA1507_12AF_11D3_AB21_00A0C98620CE_}
WriteActionCollection  : {GenerateAlert}
XmlTag                 : Rule
Name                   : Microsoft.SQLServer.2005.A_SQL_job_failed_to_complete_succ
                         essfully_1_5_Rule
Id                     : f3a5fd96-ec01-68db-09c4-02d6de2b9fa5
DisplayName            : An SQL job failed to complete successfully
Description            :
LanguageCode           : ENU
Comment                :
Status                 : Unchanged
LastModified           : 4-8-2011 9:23:17
TimeAdded              : 4-8-2011 9:23:21

ManagementGroup        : MG1
ManagementGroupId      : 2c7ee7ce-951e-5368-82e4-d17ae629c9e4
HasNonCategoryOverride : True
Enabled                : false
Target                 : ManagementPackElementUniqueIdentifier=16541255-8d63-d013-6
                         579-3d0a9065c20e
ConfirmDelivery        : True
Remotable              : True
Priority               : Normal
DiscardLevel           : 100
Category               : EventCollection
ConditionDetection     :
DataSourceCollection   : {_F6DA1507_12AF_11D3_AB21_00A0C98620CE_}
WriteActionCollection  : {GenerateAlert}
XmlTag                 : Rule
Name                   : Microsoft.SQLServer.2008.A_SQL_job_failed_to_complete_succ
                         essfully_1_5_Rule
Id                     : 80ed2394-845e-ee43-3fec-ed5bcdeec65b
DisplayName            : An SQL job failed to complete successfully
Description            :
LanguageCode           : ENU
Comment                :
Status                 : Unchanged
LastModified           : 4-8-2011 9:29:24
TimeAdded              : 4-8-2011 9:29:28

The severity property can be filtered.

Refer to the following thread for more information as to how to acquire this data:

http://social.technet.microsoft.com/Forums/systemcenter/en-US/328d5479-6ff6-49dc-b342-81f3ca70ce30/report-to-show-all-high-priority-and-critical-level-monitors-and-rules

the above script will not consider overrides for monitor or rules for priority. you can create a custom sql query to get rules/monitors with priory 1 from sql DB.

refer below link for examples.

http://blogs.technet.com/b/kevinholman/archive/2007/10/18/useful-operations-manager-2007-sql-queries.aspx

Regards

The severity property can be filtered.

Refer to the following thread for more information as to how to acquire this data:

http://social.technet.microsoft.com/Forums/systemcenter/en-US/328d5479-6ff6-49dc-b342-81f3ca70ce30/report-to-show-all-high-priority-and-critical-level-monitors-and-rules

The scripts don't output the rules and monitors based on severity. It outputs them based on priority. It seems there is no property for the cmdlet get-rule (and get-monitor) for the alert 'severity', but only for the property 'priority'.

I would like to list all rules which create a critical alert with prio 1.