Msmq Queue Not Empty Check has same TypeId as Msmq Queue Info Check

May 16, 2012 at 5:12 PM

My team is just about to start deploying Wolfpack in our organization and we found that the MsmqQueueNotEmpty check has the same TypeId as the MsmqQueueInfo check. It's my understanding that each check needs to have its own type id. Is there a reason they have the same Type Id or should they be different?

May 16, 2012 at 6:28 PM

Hi..oops..thanks for spotting it - in reality the type id/guid doesn't matter as the theory of it was to be able to identify data from a specific check "type" (as opposed to a specific instance). Eg if you wanted to find EVERY result generated by the MSMQ queue empty check you could. I think the idea was to produce a universal directory of known "check" if you wanted to write a plugin that dealt with result messages generated from a particular check you could as the is a known constant. It was also more for performing analytics on the result data.

The bottom line is a duplicate guid won't stop it working. I'll fix it in the source ASAP

If you need any help rolling out Wolfpack please drop me a message - happy to help if required.


May 16, 2012 at 9:08 PM

Thanks for your quick reply. I was aware that the type id is designed to differentiate between check types not instances of checks. The reason I asked was because my team is building a basic dashboard view that will show the current status of each of the checks grouped by the type so that we can display different metrics based on the type. 

May 17, 2012 at 8:06 AM

ok, cool....the dashboard view sounds interesting. There have been a number of enquiries about WP including a dashboard view of it's own and so far I haven't had chance to tackle this further than sketching out some ideas using SignalR (as a self hosted WP Activity) to power some html5 pages. Would be great to see a screenshot of your dashboard when you get it up and running.



May 17, 2012 at 8:09 AM

PS: The new GUID for MSMQ not empty check is: 

May 18, 2012 at 3:49 PM

Thanks, I'll try to remember to post a screen shot once we have something closer to finalization. We are using SignalR hosted in MVC3 pushing to a page using Backbone.Marionette for the views Our first phase is to have a simple overview of all of the various checks and their current state.