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

Shinken Event Handler execution required when the service state changes to CRITICAL.. #2016

Open
sjose1x opened this issue Aug 2, 2021 · 0 comments

Comments

@sjose1x
Copy link

sjose1x commented Aug 2, 2021

A service check S1 with event_handler configurated, max_attempts is 3, check interval is 5 and retry interval is 2

When this service turns to OK - WARNING the event handler executes.., also event handler invokation continues till the max_attempts are over.
Once the max_attempts are over, and then if the service check turns to WARNING - CRITICAL then the event handler did not get triggered..

Is it possible to configure event handler to get executed whenever the service turns to CRITICAL. (OK - CRITICAL OR WARNING - CRITICAL) ..?

That is regardless of first it turns to WARNING and then it becomes CRITICAL or initial problem state itself is CRITICAL

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

1 participant