[
https://issues.apache.org/jira/browse/QPID-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marnie McCormack updated QPID-326:
----------------------------------
Description:
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.
was:
In a production environment, the amoutnt of time messages are spending in the
broker on the queue may be important. Opertaors 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.
The alerts should be available both from the management console, and in the log
file where log file scraping tools may pick them up.
Summary: Allow configurable monitoring of message/queue properties
(was: Allow monitoring of how long messages are staying on queue. ALert when
oldest message passes threhold age.)
> 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
> Priority: Minor
>
> 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.
