Actionable Alerts for Web applications in Operations Manager 2007

re: Actionable Alerts for Web applications in Operations Manager 2007

John Curtiss — Thu, 04 Sep 2008 22:44:39 GMT

i've found that alerts from the Availability aggregate rollups for the web application monitors are pretty useless. i would rather have an alert that tells me which individual request failed (and now, with this description information available to me, *why* it failed) than just a blanket "hi this web app is down." the problem with turning on the unit monitor in your example is that now 2 alerts will be generated. so i always turn off alerting for the aggregate monitor and let the individual requests do the talking.

re: Actionable Alerts for Web applications in Operations Manager 2007

dhan — Thu, 04 Sep 2008 23:48:20 GMT

John, Excellent point.

Our long term approach for OpsMgr 2007, is to help minimize alerts, yet keep them meaningful. In my next blog, I intend to discuss the pros and cons of that approach and would love to have your thoughts on that discussion.

Dhananjay

re: Actionable Alerts for Web applications in Operations Manager 2007

Chad — Sat, 06 Sep 2008 03:34:05 GMT

Hello,

We have multiple web application monitors and we would like to bulk enable "content match" is this possible?

Cheers,

Chad

re: Actionable Alerts for Web applications in Operations Manager 2007

Niklas — Mon, 08 Sep 2008 14:13:13 GMT

Hi,

Really good to see that this problem is finally getting some attention.

The instructions about how to enable the monitor with a description would be ok if it was a matter of a few websites but in larger environments this is alot of work. And to have more than just the status code monitor active would require that you do all this work maybe five times for just one website or am I wrong?

Looking forward for more posts regarding this subject.

Regards,

Niklas

re: Actionable Alerts for Web applications in Operations Manager 2007

chadeb — Mon, 08 Sep 2008 21:02:29 GMT

Another problem we have is the content match test when it fails it doesn’t show in the alert what content it was looking for, I have looked all over for the parameter for this any ideas?

Cheers,

Chad

re: Actionable Alerts for Web applications in Operations Manager 2007

dhan — Tue, 09 Sep 2008 23:52:45 GMT

I will try to address as many of the concerns in upcoming posts on this topic. Please keep giving the feedback.

- Dhananjay

re: Actionable Alerts for Web applications in Operations Manager 2007

Hendrik — Thu, 11 Sep 2008 12:45:43 GMT

I try to login to a website, do some actions and logout again. The problem is that I cannot just click a logout button. The logout button has a session ID in the URL.

Is there any possibility to grab a string out of the response body and hand it over to the next request? Is there any documentation on the parameters?

Best regards,

Hendrik

re: Actionable Alerts for Web applications in Operations Manager 2007

Julius — Tue, 23 Sep 2008 21:08:36 GMT

Great information but it's painful! By default you're already getting two alerts one from the aggregate roll up which tells you "hey website is down" and then from the action step that failed. But adding this would make a THIRD alert in which the alert name is just "Base page status code" which is useless if you have multiple web applications that you're monitoring.

What would actually be useful is if the agregate roll-up actually did it's job and "rolled up" all the alerts! Take the base status code and the action step that failed into ONE alert.

re: Actionable Alerts for Web applications in Operations Manager 2007

dvo — Tue, 30 Sep 2008 22:30:35 GMT

Thank you for taking the time to do this. A question--it appears that if you have multiple requests in one web application, only the first request provides details in Health Explorer. I confirmed this by reviewing the raw data returned from a test. Only one <StatusCode> existed, so the first one returned is reused if you choose to use

$Data/Context/RequestResults/RequestResult["%ReqID%"]/BasePageData/StatusCode$

in the alert description of subsequent URL requests that fail. Is there any way to work around this, or is it by design?

Thanks again--Drew

Bulk editing monitor Alert settings and adding descriptions for Web applications

OpsMgr from SOA to .NET — Wed, 31 Dec 2008 12:08:16 GMT

It has been a while since I posted to the blog. The long break gave me a chance to work on some of the