Also @Moises we're currently looking for a way to ensure client checks are
captured despite loss of connectivity and looking at your caching mechanism
1. How are the events handled once connection is back? And what if there 2
of same events, are they sent as one event?
The caching implementation only does metrics at the moment, so it sends all
metrics at 10x rate until it transmits all cached data. It's not a lot of
work to make it work for checks, but you'd need to decide what you want to
do there. If you want to keep the history (e.g last 20 events). If a hard
disk check fails while connectivity is down, then minutes later the check
does not fail anymore and connectivity is restored, why would you want to
send an alert for something that is not a problem anymore? (e.g check disk
space got resolved on its own already). If all you want is keep a history
of when something failed even if it got resolved, then that'd require more
work because you'd need to transmit the check history to the server somehow
(currently checks just return to the server the current status).
2. How do we configure this mechanism in the Transport layer? Do you have
a documentation on this that might help us?
Sorry, not really. Perhaps Sensu 2.0 docs contain something? I know core
devs were looking at having this feature for 2.0, but I don't know if they
On Thu, Sep 21, 2017 at 10:38 PM, Kaye <email@example.com> wrote: