Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

According to Microsoft, Systems Center Operations Manager cannot monitor clustered MSMQ's on Server 2003. The Microsoft rep referenced this article. and said it applied to our problem. So, my question is: what does the serverfault community recommend to monitor msmq's in a Server 2003 cluster?

What I am looking for is something to monitor the number of messages on the queues and send an alert if messages appear on the fault queue or if the messages back-up on the main queue.


share|improve this question
up vote 1 down vote accepted

If you just want to monitor queue depth, I would break out your powershell handbook or buy your favorite developer a beer or two and look into the .NET System.Messaging namespace. You can run a scheduled task every few minutes and get near-realtime alerting that way.

share|improve this answer

I don't know about MSMQ but if it supports STOMP (and as a message broker I guess it should) you can use Perl's Net::Stomp module to send and receive a test message. I've been using following Nagios plugin to check ActiveMQ.

The point is that you can use whatever monitoring system you employ (whether it be Nagios or anything else) and check if your message broker works properly sending STOMP messages.

share|improve this answer

Here's a good resource:

MSMQ 4.0 Performance Counters and the NetNameForPerfCounters Registry Key

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.