Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] monitoring a message bus ....

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] monitoring a message bus ....


Chronological Thread 
  • From: Keith Hazelton <>
  • To: Steven Carmody <>
  • Cc: Grouper-Users <>,
  • Subject: Re: [grouper-users] monitoring a message bus ....
  • Date: Tue, 09 Apr 2013 12:16:32 -0500
  • Authentication-results: sfpop-ironport04.merit.edu; dkim=neutral (message not signed) header.i=none

I'm going to cross-post this to CIFER-Provisioning and Integration.

Curious to know specifics: Are you using an ESB? Just a JMS queue? Which
products? What do the message recipients do since most target systems don't
come knowing how to do this.

--Keith
______________________
On 2013-04-09, at 12:03 , Steven Carmody wrote:

> Hi,
>
> I know my question is only tangentially related to Grouper, but at least
> there's a link, even if its weak. Thanks for your patience with this
> question!
>
> Brown replicates group memberships from Grouper to several different target
> systems: ldap, Google, and our LMS. We expect to add other targets over
> time. When changes occur in Grouper, a msg is placed on a msg bus. A
> listener picks up that msg, and has a set of rules telling it the one or
> more targets that the msg should be forwarded to.
>
> As we become more and more reliant on this infrastructure, we're asking
> ourselves what we should monitor with respect to the bus. We're keenly
> interested in the experience of other sites with respect to what sorts of
> problems they've encountered with a bus, and what sort of monitoring we
> should implement.
>
> Is it enough to just make sure that the bus is delivering msgs? (ie have a
> separate Q used by the monitoring software). Or do we need to build
> monitoring into all the Listeners, to make sure that they are all still
> processing msgs ? Or other approaches ?
>
> Thanks in advance for sharing your experience and suggestions!




Archive powered by MHonArc 2.6.16.

Top of Page