Grouper Users - Open Discussion List

[Jeff McCullough <>]

Hi Steven,

I'm just answering your question with a question if you don't mind. How many 
groups are you provisioning this way? How are the rules setup? Are the rules 
using information in attributes stored in grouper or based upon naming or 
something else?

Thanks,
Jeff

On Apr 9, 2013, at 10:03 AM, 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!