Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Normal
Fix Version/s: Logging 5.4.2
Affects Version/s: Logging 5.3.0
Component/s: Log Collection
Labels:
- devel_ack+
- rn-done-resolved

Blocked:
False
Ready:
False
Docs QE Status:
NEW
QE Status:
VERIFIED
Release Note Text:
Before this update, several log levels (e.g. critical) documented as supported by the product were not. This update fixes the discrepancy so the documented log levels are now supported by the product.
Market:

Sprint:
Logging (Core) - Sprint 213, Logging (Core) - Sprint 214, Logging (Core) - Sprint 215, Logging (Core) - Sprint 216, Logging (Core) - Sprint 218, Logging (Core) - Sprint 219

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

The supported values for the "level" field are currently these four:

https://github.com/openshift/cluster-logging-operator/pull/1203/files#diff-620fda7d1a46cb683279924b35812d0258cb5e03dee12c3f60ec4bd93a61ad9aR478

Our documentation implies a larger set are supported:
https://docs.openshift.com/container-platform/4.8/logging/cluster-logging-exported-fields.html#level

The defaults should be expanded to match the documentation, or else the ability to pick/choose level values would be useful (to allow administrators to trade off between more coverage vs better performance)

is cloned by

LOG-2599 Supported values for level field don't match documentation