Max, There is some basic functionality in RQ to permit monitoring. You may want to take a look at the Rhino.Queues.Monitoring.PerformanceMonitor class to see what is available. This class focuses writing performance counters out to the Windows performance counters system. However you will see that it accomplishes its task by hooking into four events on the QueueManager. You can hook these events yourself for logging and other purposes. RQ also uses Log4Net extensively, so correctly configuring it may also get you what you are looking for.
As for seeing what is in the queues have a look at the Linqpad query that Corey discusses in [this post](http://groups.google.com/group/ rhino-tools-dev/browse_thread/thread/c6360af93850ea1f). I definitely feel that lack of health monitoring and visibility into queues is a sore point when using RQ in an enterprise environment. I would be happy to work with you if you were interested in adding some functionality in that area. In deed if others share my opinion that this is an area of need, I would see if I could spare some cycles to help flesh out what is currently there. --Ken On Sep 19, 7:12 am, Max <[email protected]> wrote: > Is there any way to monitor our queues when using RSB and Rhino > Queues? I would like to see what currently recides in the queues and > also able to logg messages passing through. > As far as I understand it is somewhat difficult to read directly from > the ESENT store since it's not really a multiuser database. Are there > any other ways to read the queues? Does RSB have some features that > I've missed that can be used? Anyone have made their own solution for > this? -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
