-
Feature
-
Resolution: Done
-
Major
-
None
-
None
Proposed title of this feature request
Log filtering
What is the nature and description of the request?
This feature would add options to the LogForwarding to allow administrators to spec filtering (e.g. collecting or dropping) of log messages using various options:
- log level
- by container
- by field in the record (if its json)
- by metadata
Why does the customer need this? (List the business requirements)
Customer's need this to:
- Only collect logs of significance to them (e.g. loglevel=error)
- Exclude logs from noisy containers (e.g. servicemesh side-car container)
List any affected packages or components.
- Log collection
- incorporates
-
OBSDA-289 RFE - allow custom namespace logging to infrastructure
- New
-
OBSDA-658 [RFE] Add custom configuration to vector to Filter and Reduce logs
- Closed
- is blocked by
-
LOG-2155 Filter log messages based on metadata and content.
- Closed
-
LOG-2377 Improved namespace selection for logs
- Closed
- is documented by
-
OBSDOCS-805 [DOC] Log filtering and collecting
- Closed
- is duplicated by
-
OBSDA-290 RFE - Discard/Drop logs of specific namespace (blacklist applications)
- New
- is related to
-
LOG-2827 Alternate data models for forwarded logs
- Closed
-
OBSDA-339 Filter and control size of audit logs
- Closed
-
OBSDA-105 Enable OpenShift Logging Operator Administrator to Collect Logs at the Infrastructure Namespace Level
- Closed
- relates to
-
OBSDA-80 Enable filtering in OCP 4.x collector before sending logs to third party systems
- In Progress
-
OBSDA-84 Ability to modify verbosity of logs when forwarding to external log aggregator
- Closed
- links to