You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2007/04/19 15:34:15 UTC

[jira] Updated: (QPID-393) Add alerting for Total Queue depth (across all queues)

     [ https://issues.apache.org/jira/browse/QPID-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-393:
----------------------------------

    Fix Version/s:     (was: M2)
                   M3

Moving unresolved JIRAs from M2 to M3, in preparation for M2 release

> Add alerting for Total Queue depth (across all queues)
> ------------------------------------------------------
>
>                 Key: QPID-393
>                 URL: https://issues.apache.org/jira/browse/QPID-393
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>    Affects Versions: M1
>            Reporter: Marnie McCormack
>            Priority: Minor
>             Fix For: M3
>
>
> Currently have alerting on queue depth, on a per queue basis, using a maximum threshold. User has suggested that having alerting across all queue i.e. total queue depth might be usual for max heap alerting. 
> Can see that total queue alerting is useful (though would apply caution to the notion that this would enable client applications to avoid hitting max heap size as this is near impossible !)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.