Hi Alex - first thanks for the kind words about Wolfpack - glad you like it!
I completely understand the frustration with how it works at the moment -
and you're not alone
. I have implemented a solution, a feature called "NotificationHub". Basically all messages are routed via the hub and it hosts extensible plugins that contain logic to control message delivery to the publishers. I've built
a few plugins and the one that fits your requirements is the "StateChange" NotificationMode (plugin) - it sends an alert only when the state changes - so if your error queue is empty then receives some messages it will send an alert in the next check,
subsequent checks although still in a failed state will not generate an alert.
This code is not in the 2.4 release - it was committed a while after this release and since then I've been working on v3. If you don't mind building the source then this commit contains all the NotificationHub code,
- you might need to alter the code of the check that you are using (Msmq empty check) to add the NotificationMode property so that you can hook into the NotificationHub.
Alternatively v3 in the source repository (latest) has all the checks updated to use the NotificationHub (plus some other features like a web UI to configure the checks and a signalr live alert page) - the downside to v3 at the moment is that it only supports
Let me know how you get on - I'm working on a .Net dashboard (Project 'Periscope') to allow Wolfpack to display it's alert data but I'm trying to get v3 stable and released ASAP so if you can wait that might be easier.