You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Carl Trieloff <cc...@redhat.com> on 2011/02/15 16:11:25 UTC
Re: svn commit: r1070913 - in /qpid/trunk/qpid/cpp/src: ./ qpid/broker/
qpid/cluster/
On 02/15/2011 09:17 AM, gsim@apache.org wrote:
> Author: gsim
> Date: Tue Feb 15 14:17:45 2011
> New Revision: 1070913
>
> URL: http://svn.apache.org/viewvc?rev=1070913&view=rev
> Log:
> QPID-3002: Configurable threshold alerts for queues
>
Why did we not add configurable thresholds to QMF. i.e. update the agent
to be able
to set a high & low water mark in the agent and then generate an event
based on hitting that limit for
any counter.
I would think we would create a generic mechanism eventually, so I'm
concerned we introduce a
specific mechanism for queue only to replace it with a generic mechanism
in a few months time which
will be bad if we change the way they are configured.
thoughts?
Carl.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: svn commit: r1070913 - in /qpid/trunk/qpid/cpp/src: ./ qpid/broker/
qpid/cluster/
Posted by Gordon Sim <gs...@redhat.com>.
On 02/15/2011 03:11 PM, Carl Trieloff wrote:
> On 02/15/2011 09:17 AM, gsim@apache.org wrote:
>> Author: gsim
>> Date: Tue Feb 15 14:17:45 2011
>> New Revision: 1070913
>>
>> URL: http://svn.apache.org/viewvc?rev=1070913&view=rev
>> Log:
>> QPID-3002: Configurable threshold alerts for queues
>>
>
>
> Why did we not add configurable thresholds to QMF. i.e. update the agent
> to be able
> to set a high & low water mark in the agent and then generate an event
> based on hitting that limit for
> any counter.
A generic mechanism was more complicated than my use cases required. I
wanted to get something in for the 0.10 release (as previously
advertised by QIP and Jira) and kept things as simple as possible.
> I would think we would create a generic mechanism eventually, so I'm
> concerned we introduce a
> specific mechanism for queue only to replace it with a generic mechanism
> in a few months time which
> will be bad if we change the way they are configured.
I'm quite confident we can mitigate that if and when someone does
propose a generic mechanism.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org