-
Epic
-
Resolution: Done-Errata
-
Normal
-
Logging 6.0.0
-
logging-otel
-
20
-
False
-
None
-
False
-
Yellow
-
NEW
-
Administer, API, Release Notes
-
To Do
-
OBSDA-498 - Enable OpenTelemetry in Cluster Logging Operator
-
OBSDA-498Enable OpenTelemetry in Cluster Logging Operator
-
NEW
-
0% To Do, 0% In Progress, 100% Done
-
This release enables a tech-preview of log forwarding using the OpenTelemetry Observability Framework. A new output type (otlp) enables sending JSON encoded log records using the OpenTelemetry data model and general resource semantic conventions
-
Feature
-
M
Goals
Log collector to emit JSON log records using the Open Telemetry logs data model and general resource semantic conventions.
References
Non-Goals
- No store or console support for the OTEL model - future story.
- Initial use case is to allow forwarding logs off-cluster to an OTEL receiver.
Motivation
- Rising popularity of OTEL, integrate with external systems based on OTEL.
- Possible future use of OTEL as a common language with other observability tools.
Alternatives
Ignore OTEL.
Acceptance Criteria
- CLO optionally forwards valid OTEL logs to external OTEL collector
- Forwarding of Viaq logs is unaffected
- Verify functionality is guarded behind a feature gate
Risk and Assumptions
- Complicates the CLO
- Alternate views of the same log data are confusing if consumed in the same cluster.
- May create a need for further OTEL work (store, console)
Documentation Considerations
- Update API reference doc
Usecase example of writing to RH managed lokiStack- Usecase example of writing to OTEL collector
- New reference document or redirect to OpenTelementry semantic conventions we use
- Viaq/OTEL translation table, side by side with definitions.
Open Questions
Additional Notes
- is related to
-
LOG-2827 Alternate data models for forwarded logs
- Closed
-
LOG-5125 Disable API and feature gate for OTEL
- Closed
- links to
-
RHBA-2024:137361 Logging for Red Hat OpenShift - 6.0.0
(3 links to)