-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
buggy count comparison filter in 0.4.3 and 0.4.4 #297
Comments
I also find count cant not work.. |
Did som research... One of the developers confirmed that there is no workaround and that this bug wasn't fixed until the relase of 0.5.0.2 -> https://github.com/mickem/nscp/releases/tag/0.4.4.2 |
Yes, one of the main changes in 0.5.0 was essentially the fix for this issue. You can work around it using custom scripts in earlier versions. |
As for the other issue do you mean COUNT versus count or foo = "bar" versus foo = "BAR"? |
Hi mickem! Some processes may written differently, like explorer.exe or Explorer.exe, but mean the very same process. |
Thanks for the information mickem The other issue was explained by MaskierterMuchacho very good, exactly hit the spot |
I was just about to say thats what regular expression and like are for but noticed that like did not ignore case, wil lbe fixed in the next build. So:
should match:
|
Got some problems with count and <, > and =
The following example: Want to check if 2 of 3 processes are started
nscp.exe client -q check_process "filter=exe = 'aaa.exe' or exe = 'bbb.exe' or exe = 'ccc.exe'" process=* "warn=count < 2 " "crit=count < 1 " WARNING: aaa.exe=started|'count'=2;2;1
In the result you can see that there are two processes started, but output is only processed for one and state is critical, even if 2 is not lower than 2
After alot of testing I could not find a working solution
Tested the following two examples and a lot more (!=, =, <,...":
"warn=count < 2 " "crit=count < 1 "
"warn=count = 1 " "crit=count = 0 "
Furthermore filter rules are case sensitive, it would be nice to have possibility to use them non case sensitive
The text was updated successfully, but these errors were encountered: