This should be just a matter of selecting an ‘Alert Type’ of “outbound queue depth” for the desired thread, and spedifying >= 50. For the duration, I’ll normally select a duration of ‘N minutes’ and then set it for 5 (or whatever makes sense for that thread). Specifying a duration of N minutes means that the queue must be >= 50 for N minutes; this prevents the alert from firing prematurely if you get a big burst of transactions that causes the queue to jump to 50 or above for just a few seconds.
If you’re asking if the alert will display the current queue depth as part of the alert message, then the answer would be “No”; the alert message displays the criteria that was met to trigger the alert – i.e. “OB queue depth >= 50 for 600 seconds”. However, to address the second part of your question, you can define a single alert with the same criteria, selecting multiple connections for the ‘Source’, and simply select “any” as your ‘Source Count’; then if any one of the connections meets the criteria, the alert would trigger and the alert message would indicate the connection that triggered the alert.
Hope this helps.
Jim Cobane
Henry Ford Health
Author
Replies
Viewing 2 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.
.
.