Grouper Users - Open Discussion List

[Jim Fox <>]

We do something like your guess. We allow any app to send udp
datagrams to a generic 'is-it-running' monitor.  But that's a
different thing.  It monitors that the listener is running.

As the originator of messages I don't really care if a particular
listener is running or not.  I may not even know them all.
I just send.  Although I do guarantee at least one message every
fifteen minutes.

As listener on the bus I want to make sure that messages are getting
to me, so I report an error if I don't get anything for twenty
minutes.  This error report goes to the admins of the listener.

I'll note that if, as sender, I didn't also just happen to manage
one of the listeners I would create one just to make sure the
message bus is working.

Jim



On Wed, 10 Apr 2013, Steven Carmody wrote:

> Date: Wed, 10 Apr 2013 07:04:53 -0700
> From: Steven Carmody 
> <>
> To: Jim Fox 
> <>
> Cc: Grouper-Users 
> <>
> Subject: Re: [grouper-users] monitoring a message bus ....
>
> On 4/9/13 1:43 PM, Jim Fox wrote:
> > Our standard method is to send heartbeat messages every 10 or 15
> > minutes. If a client doesn't see anything for longer than that
> > there's an error somewhere. That works with all message systems.
> >
> > Amazon has a service, CloudWatch, that allows you to configure
> > email, or some other signal, when certain conditions are met:
> > no SNS message for xx minutes, etc. We use that too.
>
> Jim -- thanks once again!
>
> A quick question, so I don't jump to the wrong conclusions -- I'm guessing 
> that your "listeners" send the heartbeat msg to the monitor client ?