-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z
-
Quality / Stability / Reliability
-
False
-
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
In OCP console while filtering the logs, its observed the logs with level default,metadata,notice,etc are not displayed when we filter the logs using severity unknown
Version-Release number of selected component (if applicable):
4.14+
How reproducible:
100% reproducible
Steps to Reproduce:
1. Deploy a cluster with loki 2. create a test application,make sure it has log with level as default 3. Filter the logs with severity set to unknown 4. No data is played, Change teh query manually and set level to what is there in the logs
Actual results:
Logs filters working incorrectly
Expected results:
Unknown level should display logs with all the loglevel
Additional info:
I would also request to change the name of the filter from unknown to unclassified which will display all the log with level that is not equal to any of critical/error/warning/debug/info/trace Query to be used { log_type="application" } | json | level!~"(?i)critical|emerg|fatal|alert|crit|error|err|eror|warn|warning|debug|dbug|info|inf|information|notice|trace" { log_type="infrastruture" } | json | level!~"(?i)critical|emerg|fatal|alert|crit|error|err|eror|warn|warning|debug|dbug|info|inf|information|notice|trace" { log_type="audit" } | json | level!~"(?i)critical|emerg|fatal|alert|crit|error|err|eror|warn|warning|debug|dbug|info|inf|information|notice|trace"