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

Search in log by severiry level #59

Closed
fbetil opened this issue Mar 3, 2016 · 3 comments
Closed

Search in log by severiry level #59

fbetil opened this issue Mar 3, 2016 · 3 comments
Assignees
Labels
Milestone

Comments

@fbetil
Copy link

fbetil commented Mar 3, 2016

When searching in log by "severity level scanner", dropdown show options " >= " and " = ".
So, in example, it's not possible to search for a most critical level than "WARN", because "A lower number represents critical severity and a higher number a more informative severity." (that's in the filters log configuration).
Thanks,

@mbok mbok added this to the 0.5.3 milestone Mar 4, 2016
@mbok mbok self-assigned this Mar 4, 2016
@mbok mbok added the bug label Mar 4, 2016
@mbok
Copy link
Owner

mbok commented Mar 4, 2016

You are right! The filter defines the right order which is inspired by syslog.
The level scanner is an older component born together with the log4j reader with the wrong - reverse ordering interpretation.
I'll fix the log4j reader and add to the severity scanner all possible operands: "<", "<=" and "!=".

@mbok
Copy link
Owner

mbok commented Mar 4, 2016

Fixed in release 0.5.3. Please download here: https://github.com/logsniffer/logsniffer/releases/tag/0.5.3

@mbok mbok closed this as completed Mar 4, 2016
@fbetil
Copy link
Author

fbetil commented Mar 7, 2016

That's works fine !
Thanks.

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

No branches or pull requests

2 participants