all Technical posts

SCOM: Availability Monitor for suspended orchestrations

Let's take a deeper look into the default monitoring for suspended orchestrations and the alerts it generates. Certainly a timesaver if you need to keep a close eye on your suspended instances.

Recently I wrote a post about advanced orchestration monitoring for BizTalk Server using System Center Operations Manager (SCOM).

There, I wrote about some of the shortages in the default monitor. In less critical environments the default monitoring for suspended orchestrations will be sufficient in most cases. I bumped into the same issue a couple of times now and I would like to share it with you, hoping it saves you some troubleshooting. For us, Codit Managed Services, it’s very important to receive the right alerts when instances get suspended.

This blog post concerns the default monitor for suspended orchestrations and the alerts it generates.
I often hear following question: “My orchestration is suspended for 4 hours now and still I didn’t receive any alerts about it?!”. At first I also did not find an explanation for this. Let’s take a deeper look at this monitor.

If you have currently suspended orchestrations on your environment you should see them in the SCOM console having a critical or a warning state:

Capture7

If you open the Health Explorer for this Orchestration you can see some history concerning the health state:

Capture2

Now the question rises: “Why am I not receiving an alert even while my orchestration has a warning state…. ?”.

If we take a look at the properties of the monitor at first sight everything seems to be correctly enabled:

Capture4

I also missed it several times, but then I took a look at the first property. “Alert on State”.

When you check the possible options of the property you will see 2 options. Choose the second one! Default a warning state will trigger no alerts!

Capture5

The warning limit (the last property) has a default value of 10, so more then 10 orchestrations of the same type should be suspended before an alert is triggered…. If you change the “Alert on State” property you will always receive alerts when your environment contains a suspended orchestration instance, no matter how many instances.

But remember, as soon as the monitor is in a critical state you will no longer receive an alert when new instances get suspended! If you want an alert per instance, check out my previous post about advanced orchestration monitoring.

Subscribe to our RSS feed

Thanks, we've sent the link to your inbox

Invalid email address

Submit

You will receive the White Paper in your mailbox. Don’t hesitate to contact us for more information.

Stay in Touch - Subscribe to Our Newsletter

Keep up to date with industry trends, events and the latest customer stories

Invalid email address

Submit

Great you’re on the list!