Hi all, I'm having trouble setting up a static threshold monitor for a specific queue created with MSMQ 3 on Win3K R2. The management pack I'm using for MSMQ on SCOM R2 is v6.0.6615.0 (contains the fix for monitoring MSMQ on a failover cluster). The issue is that when I set up the monitor and selecting the performance counter, I cannot see the specific queue on the cluster or on any of the nodes. However, MSMQ did detect the queue and it is collecting statistics for it corretly (I can see the graphs in the performance view and its 100% correct). Is there any trick to seeing the queue on the cluster? I've tried monitoring "all instances" under the performance counter but no luck. Any ideas? Thanks! AvdV

I think you are saying you are trying to set up a windows performance counter monitor on a clustered computer pair. Have you tried using the cluster virtual as the computer name for selecting the performance counter name? If you know accurately what the performance counter name will be, then you can just set up the performance counter monitor and type in the object and counter name. It isn't clear what you are trying to do with a particular queue. The MP, as you say, finds the queue, yes? Since the MP is collecting performanc counters correctly, you may want to look at those for a hint.Microsoft Corporation

I'm trying to create a static threshold monitor for a MSMQ queue thats been set up on a failover cluster. SCOM is collecting performance data correctly for the queue, but when setting up the monitor, no queues are listed / detected when selecting the MSMQ object. This is the same when selecting either of the cluster nodes or the virtual instance. I also tried manually typing the queue info and depoying it to the cluster, but no alears are raised when the monitor threshold is reached. I'm sure its a simple thing I'm going wrong ...AvdV

You issue is simply that you are assuming you can use a perfmon datasource to monitor these performance statistics. The perf counters you see in the console collected are NOT standard perfmon datasources. That is why when you try and monitor one of the perf counters, and go to perfmon - they do not exists. These performance statistics are created via the MP via script. The script submits the data as a propertybag, and then the bag data is mapped to performance data. All of these collection rules utilize the Microsoft.MSMQ.2003.DataSource.Queue.Statistics.PerformanceRaw datasource. Each rule passes some cofniguration data, in the form of the counter name, to this script based datasource. This is a composite datasource which contains Microsoft.MSMQ.2003.DataSource.Queue.Statistics.PropertyBag datasource, and a Condition Detection module which handles the performance mapping. The propertybag datasource contains the script: QueueStatistics.vbs So - as you can see - these are not simple performance counter based workflows. The MSMQ team would need to create these as simple perf counters in a future version to instrument simpler monitoring. As it is now - you can use this script/script datasource in your own custom monitoring, but you will need to build your own MonitorType that adds condition detections to drive monitor state based on the propertybag output of the script.Kevin Holman

Many thanks Kevin - much appreciated.AvdV