Hi List,
I’m using roundrobin subscribers to distribute public type checks amongst my sensu clients & this is working great.
The only issue I’m having is that each check appears to be unique from an event POV, for instance I will get events generated & handled for every subscriber rather than the check being a singleton.
I can’t quite figure out from the documentation how to essentially group the checks such that regardless of where they are executing there’s only a single event then subsequent handle.
Do I need to make a custom handler which is looking for duplicates or is this what aggregates are for?
Any clues would help please.
Regards, Lee
This is achieved by setting a consistent "source" for the alerts:
https://sensuapp.org/docs/latest/checks#anatomy-of-a-check-definition
···
On Mon, Aug 24, 2015 at 8:22 PM, Lee Webb <nullify005@gmail.com> wrote:
Hi List,
I'm using roundrobin subscribers to distribute public type checks amongst my
sensu clients & this is working great.
The only issue I'm having is that each check appears to be unique from an
event POV, for instance I will get events generated & handled for every
subscriber rather than the check being a singleton.
I can't quite figure out from the documentation how to essentially group the
checks such that regardless of where they are executing there's only a
single event then subsequent handle.
Do I need to make a custom handler which is looking for duplicates or is
this what aggregates are for?
Any clues would help please.
Regards, Lee
Can you explain how you configured the round robin checks?