-
Notifications
You must be signed in to change notification settings - Fork 44
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
New operand XOR or MAX 1 #206
Comments
Hi, thanks for the suggestion. That's definitely something I think is a good addition. Though, for now there's no chance it goes into the upcoming release. Maybe the next. In case you can't wait, try this:
🤣 |
On my machine, the config workaround shown does not work for the scenario described above. The root node becomes CRITICAL if any of its nodes are CRITICAL, but should be OK. |
Strange... the workaround currently works for me too. Don't know what I have tested. I'm pretty sure it didn't work yesterday. Nevertheless, I have submitted a pull request to implement "MAX 1" for the current development version. |
Expected Behavior
I would like to define a node in which only one of 2 children is allowed to be OK at the same time.
CRITICAL + CRITICAL = CRITICAL
OK + CRITICAL = OK
CRITICAL + OK = OK
OK + OK = CRITICAL
Current Behavior
OR works for the first 3 cases.
MIN 1 works for the first 3 cases.
NOT works for the last 3 cases.
Possible Solution
Addition of a new operand - XOR or MAX 1.
Context
I have identical checks for a service on 2 servers but only one is allowed to run.
If both run race conditions and duplication of data could occur.
The text was updated successfully, but these errors were encountered: