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
0.4.3.131 and check_service - state_is_ok() does not work as expected #130
Comments
state_ok and state_perfect are in essence macros for working with delayed services. so a service which is delayed is not a critical state. If you want to check if a service is started use the started and running and such values instead.
|
or
Which logs this:
|
Command should be:
The filter needs 'qoute' around strings |
OK great that's the key thing I was missing, thanks for that. Is there a way to disable the performance data being returned by check_service ?
I tested with 0.5.0.17 and I get the same output. |
sort of... something along the lines of: "perf-config=*(ignored:true)" |
Interestingly enough when testing this I got no performance data... wonder if I have broken something... Here you hva it for check_spu (should work the same):
|
Got it, works a treat thanks very much.
I did check the manual first but perf-config is in a to-do state. I just double checked and the perfdata comes out (in 0.4.3.121 or 0.5.0.17) however using the perf-config stops it anyway. |
FYI it seems as though when you add the "critical=state = 'stopped'" it adds the performance data.
|
perfdata should be there always I think... Ill reopen for now... |
Lets say I have a service that I want to be in a stopped state. So it's OK when it's stopped and Critical when it's running.
Here is the output when the service is running:
This is correct, it should be critical because it is running.
Here is the output when the service is stopped:
This is wrong in reporting WARNING, it should be reporting OK.
Am I using the syntax correctly? I've also tried:
The text was updated successfully, but these errors were encountered: