Comments on: It’s bound to happen: How to handle alert storms http://pavleck.net/2008/10/06/its-bound-to-happen-how-to-handle-alert-storms/ Monitoring, Scripting, and other Technologies Tue, 06 Jan 2009 23:23:00 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Stefan Stranger's Weblog - Manage your IT Infrastructure : New OpsMgr Tool: OpsMgr Alert Closer http://pavleck.net/2008/10/06/its-bound-to-happen-how-to-handle-alert-storms/comment-page-1/#comment-83 Stefan Stranger's Weblog - Manage your IT Infrastructure : New OpsMgr Tool: OpsMgr Alert Closer Tue, 04 Nov 2008 08:40:20 +0000 http://pavleck.net/?p=101#comment-83 [...] beta, so Jeremy would love it if you all could test it out for him. This is a perfect solution to handle those pesky alert storms and another tool in the [...] [...] beta, so Jeremy would love it if you all could test it out for him. This is a perfect solution to handle those pesky alert storms and another tool in the [...]

]]> By: Pavleck.Net » Blog Archive » New Contest and a new utility: SCOM-CloseAll http://pavleck.net/2008/10/06/its-bound-to-happen-how-to-handle-alert-storms/comment-page-1/#comment-82 Pavleck.Net » Blog Archive » New Contest and a new utility: SCOM-CloseAll Mon, 03 Nov 2008 22:05:11 +0000 http://pavleck.net/?p=101#comment-82 [...] It’s bound to happen: How to handle alert storms [...] [...] It’s bound to happen: How to handle alert storms [...]

]]> By: Jeremy D. Pavleck http://pavleck.net/2008/10/06/its-bound-to-happen-how-to-handle-alert-storms/comment-page-1/#comment-77 Jeremy D. Pavleck Mon, 20 Oct 2008 21:17:11 +0000 http://pavleck.net/?p=101#comment-77 Ah, good point AJ! If you want the same alert information in a more 'OpsMgr MS acceptable' method, you can also run the "Most Common Alerts" report under the Reporting tab. Ah, good point AJ!
If you want the same alert information in a more ‘OpsMgr MS acceptable’ method, you can also run the “Most Common Alerts” report under the Reporting tab.

]]> By: AJ http://pavleck.net/2008/10/06/its-bound-to-happen-how-to-handle-alert-storms/comment-page-1/#comment-74 AJ Fri, 17 Oct 2008 06:29:38 +0000 http://pavleck.net/?p=101#comment-74 Thanks for posting this, handy escape route if the console's throwing a wobbly. I notice that "SELECT Count(*) FROM Alert" you suggested here shows all alerts that haven't been groomed regardless of open/closed state. The result of that query came out around the 6 million alert mark for me (99.99% were closed). I've manually kicked off the grooming stored proc to see whether it permanently cuts the numbers there and something just went awry in the nightly cleanup. To figure out what to tune I've ended up running "select alertname, count(*)as x from alert(nolock) group by alertname order by x" to locate the worst offenders. Thanks for posting this, handy escape route if the console’s throwing a wobbly.

I notice that “SELECT Count(*) FROM Alert” you suggested here shows all alerts that haven’t been groomed regardless of open/closed state. The result of that query came out around the 6 million alert mark for me (99.99% were closed).

I’ve manually kicked off the grooming stored proc to see whether it permanently cuts the numbers there and something just went awry in the nightly cleanup.

To figure out what to tune I’ve ended up running “select alertname, count(*)as x from alert(nolock) group by alertname order by x” to locate the worst offenders.

]]>