We are using SCOM 2007 R2 to monitor BizTalk 2010. I notice that alerts generated by monitors are automatically resolved and set to Closed once the error is resolved. However, alerts generated by rules are not auto-resolved even when the source for alert is resolved. Is there any way I can set alerts generated by rules also to automatically close when it returns to healthy state, I do not want to specify number of days as the criteria to auto-resolve, rather the source of error returning to healthy as the criteria. This is very critical to meet our project requirements. Appreciate your suggestions and help. Thanks a lot.

> Is there any way I can set alerts generated by rules also to automatically close when it returns to healthy state No, you can't set autoclose to rule generated alerts. It's by design.http://OpsMgr.ru/

Thanks. Our project requirements need us to send an email alert for every occurence of the alert. Due to the way its designed, the email alert goes only on the first occurence of the alert (generated by a rule), for every subsequent occurence, it simply increments the count by 1 but no email is sent. Unless the administrator manually closes an alet, for every subsequent occurence, no email will go. Is there anything I can to notify administrator on every alert occurence ? Can I create an override and modify the alert suppresion for the rule ? I am new to SCOM and appreciate your help. Thanks !

Read this: http://blogs.msdn.com/b/mariussutara/archive/2007/11/07/alert-suppression-beginning.aspx >Can I create an override and modify the alert suppresion for the rule ? In some cases you'll have to recreate a rules.http://OpsMgr.ru/

Hi To be honest, I'd go back and question your project requirements as they don't make much sense. All that will happen is that the customer will be spammed by email and spend all day managing the emails rather than using OpsMgr to manage their environment. They will eventually (probably sooner rather than later) just start to ignore emails and OpsMgr becomes irrelevant and the project fails. Perhaps explain to the customer how OpsMgr works as even if they decide to use it as a spam generating tool, you won't be able to get it to work this way without a huge amount of customisation (e.g. disable all the rules and recreate them to remove suppression). Note that not all monitors auto-resolve either so you need to consider these as well as alerts. Out of interest - why do they need an email for every alert? There is an alert in the console already that they can see. Good Luck GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Thanks Graham. I agree that there will be a flooding of emails if we remove suppression for all rules and those monitors where auto-resolve is not designed. I think, we will have the default design , to notify only on the first occurence of an alert. Thanks !

Maybe the application needs to be better instrumented; there is a great monitor called "Windows Event Reset" that will generate an alert when an event in the NT event log is generated and will close the alert when a different event is generated (for example, the "I'm broken" event ID is 100 and the "I'm OK event is 101 - when the 100 is raised, an alert is generated and then when 101 is raised, the alert gets resolved)."Fear disturbs your concentration"

That would be a monitor and not a rule ... The major difference here is that rules are designed for the older type of "pass to a ticketing system". Not having suppression is an option on the rule definition. A new alert can be generated for each occurrence of an event, but then the costs would increase since someone would have to spend time closing alerts on the same number as there were underlying events.Microsoft Corporation