You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by "Gibson, Jack" <ja...@paypal.com.INVALID> on 2015/09/03 17:25:11 UTC
Subscribing to Dispatch Router Events
Trying to figure out if there is an easy way to subscribe to router events like we can with the QMF console? Currently, we are repeatedly calling the $management address but that's a bit wonky. Any pointers would be great.
Jack
Gibson, Jack
Chief Architect - Core Payments Platforms
PayPal
Re: Subscribing to Dispatch Router Events
Posted by Chuck Rolke <cr...@redhat.com>.
----- Original Message -----
> From: "aconway" <ac...@redhat.com>
> To: users@qpid.apache.org
> Sent: Thursday, September 3, 2015 5:45:58 PM
> Subject: Re: Subscribing to Dispatch Router Events
>
> On Thu, 2015-09-03 at 19:07 +0000, Gibson, Jack wrote:
> > Alan -
> >
> > Pretty much what I was thinking. We should be able to create
> > multiple
> > subscriptions per link/session/connection that allow you to specify
> > either
> > a selector or filter such that you can receive notifications of
> > monitorable or actionable events such as link/connection failures,
> > connects/disconnects, address registration, message counts, etc.
> > Also
> > from an enterprise perspective, syslog works ok as we can use syslog
> > -ng
> > piping to splunk or something. But, it would be nice to be able to
> > ³inject² a log implementation kinda like you do with Spring in the
> > java
> > world to allow folks to use other logging facilities.
>
> Yep. We do syslog and files (and in principle could do others, maybe
> even some form of user python plugin) for dispatch log statements in
> code (like qpid) but in qpid we never did integrate management event
> logging with the rest of the logging. I think for dispatch we should,
In qpid broker the management events are fully supported with normal
logging. Part of adding --log-disable was to shut off the vebose
Management category. Anything shown by print_events is in the normal
log. Maybe I'm missing a finer qualification about the integration.
> and have a text form of management events be just another logging
> category so we can provide the logging integration in one place.
>
> That's not a replacement for programmatic notifications where you want
> to take action rather than just log, but it's a useful step.
>
> >
>
> >
> > Jack
> >
> >
> > On 9/3/15, 1:53 PM, "aconway" <ac...@redhat.com> wrote:
> >
> >
> > > On Thu, 2015-09-03 at 11:57 -0400, Ted Ross wrote:
> > > > Jack,
> > > >
> > > > We have not implemented any form of notification in the
> > > > management
> > > > agent
> > > > yet. This is something we are interested in providing and also
> > > > contributing to the in-progress management specification at
> > > > OASIS.
> > > >
> > > > -Ted
> > > >
> > > > On 09/03/2015 11:25 AM, Gibson, Jack wrote:
> > > > > Trying to figure out if there is an easy way to subscribe to
> > > > > router
> > > > > events like we can with the QMF console? Currently, we are
> > > > > repeatedly calling the $management address but that's a bit
> > > > > wonky.
> > > > > Any pointers would be great.
> > > > >
> > > > > Jack
> > >
> > > Attached is a draft I proposed to the the AMQP-TC, the discussion
> > > thread is at: http://markmail.org/thread/k2ekcgb5wu23yirv - the
> > > draft
> > > may be a bit out of date with the discussion.
> > >
> > > Generally it has met with approval next step is for me to actually
> > > implement something in dispatch. Very interested in your feedback
> > > when
> > > I do. At least one other TC member has expressed interest in
> > > implementing it for the Qpid Java broker but no code yet.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Subscribing to Dispatch Router Events
Posted by aconway <ac...@redhat.com>.
On Thu, 2015-09-03 at 19:07 +0000, Gibson, Jack wrote:
> Alan -
>
> Pretty much what I was thinking. We should be able to create
> multiple
> subscriptions per link/session/connection that allow you to specify
> either
> a selector or filter such that you can receive notifications of
> monitorable or actionable events such as link/connection failures,
> connects/disconnects, address registration, message counts, etc.
> Also
> from an enterprise perspective, syslog works ok as we can use syslog
> -ng
> piping to splunk or something. But, it would be nice to be able to
> ³inject² a log implementation kinda like you do with Spring in the
> java
> world to allow folks to use other logging facilities.
Yep. We do syslog and files (and in principle could do others, maybe
even some form of user python plugin) for dispatch log statements in
code (like qpid) but in qpid we never did integrate management event
logging with the rest of the logging. I think for dispatch we should,
and have a text form of management events be just another logging
category so we can provide the logging integration in one place.
That's not a replacement for programmatic notifications where you want
to take action rather than just log, but it's a useful step.
>
>
> Jack
>
>
> On 9/3/15, 1:53 PM, "aconway" <ac...@redhat.com> wrote:
>
>
> > On Thu, 2015-09-03 at 11:57 -0400, Ted Ross wrote:
> > > Jack,
> > >
> > > We have not implemented any form of notification in the
> > > management
> > > agent
> > > yet. This is something we are interested in providing and also
> > > contributing to the in-progress management specification at
> > > OASIS.
> > >
> > > -Ted
> > >
> > > On 09/03/2015 11:25 AM, Gibson, Jack wrote:
> > > > Trying to figure out if there is an easy way to subscribe to
> > > > router
> > > > events like we can with the QMF console? Currently, we are
> > > > repeatedly calling the $management address but that's a bit
> > > > wonky.
> > > > Any pointers would be great.
> > > >
> > > > Jack
> >
> > Attached is a draft I proposed to the the AMQP-TC, the discussion
> > thread is at: http://markmail.org/thread/k2ekcgb5wu23yirv - the
> > draft
> > may be a bit out of date with the discussion.
> >
> > Generally it has met with approval next step is for me to actually
> > implement something in dispatch. Very interested in your feedback
> > when
> > I do. At least one other TC member has expressed interest in
> > implementing it for the Qpid Java broker but no code yet.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Subscribing to Dispatch Router Events
Posted by "Gibson, Jack" <ja...@paypal.com.INVALID>.
Alan -
Pretty much what I was thinking. We should be able to create multiple
subscriptions per link/session/connection that allow you to specify either
a selector or filter such that you can receive notifications of
monitorable or actionable events such as link/connection failures,
connects/disconnects, address registration, message counts, etc. Also
from an enterprise perspective, syslog works ok as we can use syslog-ng
piping to splunk or something. But, it would be nice to be able to
³inject² a log implementation kinda like you do with Spring in the java
world to allow folks to use other logging facilities.
Jack
On 9/3/15, 1:53 PM, "aconway" <ac...@redhat.com> wrote:
>On Thu, 2015-09-03 at 11:57 -0400, Ted Ross wrote:
>> Jack,
>>
>> We have not implemented any form of notification in the management
>> agent
>> yet. This is something we are interested in providing and also
>> contributing to the in-progress management specification at OASIS.
>>
>> -Ted
>>
>> On 09/03/2015 11:25 AM, Gibson, Jack wrote:
>> > Trying to figure out if there is an easy way to subscribe to router
>> > events like we can with the QMF console? Currently, we are
>> > repeatedly calling the $management address but that's a bit wonky.
>> > Any pointers would be great.
>> >
>> > Jack
>
>Attached is a draft I proposed to the the AMQP-TC, the discussion
>thread is at: http://markmail.org/thread/k2ekcgb5wu23yirv - the draft
>may be a bit out of date with the discussion.
>
>Generally it has met with approval next step is for me to actually
>implement something in dispatch. Very interested in your feedback when
>I do. At least one other TC member has expressed interest in
>implementing it for the Qpid Java broker but no code yet.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Subscribing to Dispatch Router Events
Posted by aconway <ac...@redhat.com>.
On Thu, 2015-09-03 at 11:57 -0400, Ted Ross wrote:
> Jack,
>
> We have not implemented any form of notification in the management
> agent
> yet. This is something we are interested in providing and also
> contributing to the in-progress management specification at OASIS.
>
> -Ted
>
> On 09/03/2015 11:25 AM, Gibson, Jack wrote:
> > Trying to figure out if there is an easy way to subscribe to router
> > events like we can with the QMF console? Currently, we are
> > repeatedly calling the $management address but that's a bit wonky.
> > Any pointers would be great.
> >
> > Jack
Attached is a draft I proposed to the the AMQP-TC, the discussion
thread is at: http://markmail.org/thread/k2ekcgb5wu23yirv - the draft
may be a bit out of date with the discussion.
Generally it has met with approval next step is for me to actually
implement something in dispatch. Very interested in your feedback when
I do. At least one other TC member has expressed interest in
implementing it for the Qpid Java broker but no code yet.
Re: Subscribing to Dispatch Router Events
Posted by Ted Ross <tr...@redhat.com>.
Jack,
We have not implemented any form of notification in the management agent
yet. This is something we are interested in providing and also
contributing to the in-progress management specification at OASIS.
-Ted
On 09/03/2015 11:25 AM, Gibson, Jack wrote:
> Trying to figure out if there is an easy way to subscribe to router events like we can with the QMF console? Currently, we are repeatedly calling the $management address but that's a bit wonky. Any pointers would be great.
>
> Jack
>
> Gibson, Jack
> Chief Architect - Core Payments Platforms
> PayPal
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org