You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org> on 2007/12/12 13:24:43 UTC

[jira] Resolved: (QPID-326) Allow configurable monitoring of message/queue properties

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

Rob Godfrey resolved QPID-326.
------------------------------

       Resolution: Fixed
    Fix Version/s: M2

> Allow configurable monitoring of message/queue properties 
> ----------------------------------------------------------
>
>                 Key: QPID-326
>                 URL: https://issues.apache.org/jira/browse/QPID-326
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>            Reporter: Rob Godfrey
>            Assignee: Robert Greig
>            Priority: Minor
>             Fix For: M2
>
>         Attachments: qpid-326.patch
>
>
> In a production environment, the amount of time messages are spending in the broker on the queue may be important.  Operators may wish to be informed if that time exceeds a threshold level.
> The threshold level should be configurable... and the alert should only repeat after the on-queue wait time has fallen below a separate lower threshold level, to prevent an alert storm.
> Also want to be able to log queue depth and similarly configure alert logging at a threshold.
> The alerts should be available both from the management console, and in the log file where log file scraping tools may pick them up.

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