Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No alert when critical events happen in silence period #182

Open
jimzhou2010 opened this issue Oct 26, 2017 · 2 comments
Open

No alert when critical events happen in silence period #182

jimzhou2010 opened this issue Oct 26, 2017 · 2 comments

Comments

@jimzhou2010
Copy link

jimzhou2010 commented Oct 26, 2017

Test process:

  1. Silence a check
  2. Then make the check from 0 (ok) to 2 (critical)
  3. After the silence expired, check still in critical status, but won't receive any alter unit refresh time reach.
  4. sensu-server log showing ""output":"only handling every 144 occurrences" (144 is refresh time/interval time)

Therefore, If in silence/stash period, any checks become critical, and after the time the silence expired, we still can't know the critical checks.

After silence expired, the critical occurrences is great than check occurrences setting, so that sensu won't trigger alert and just bail a "only handling every 144 occurrences".

Anyone can help checking on the issue ?

Appreciate for any help

@majormoses
Copy link
Member

I feel like this needs to be addressed in the occurrences gem. ping @cwjohnston

@majormoses
Copy link
Member

We might want another value to track so that we could say occurrences and occurrences_after_silence attributes so that we can handle that scenario better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants