-
Story
-
Resolution: Done
-
Major
-
None
-
3
-
False
-
None
-
False
-
NEW
-
OBSDA-849 - Enable Full In-Cluster OpenTelemetry Support In OpenShift Logging
-
NEW
-
Release Note Not Required
-
-
-
Log Storage - Sprint 258, Log Storage - Sprint 259, Log Storage - Sprint 260, Log Storage - Sprint 261, Log Storage - Sprint 262
As an administrator, I want to control which OpenTelemetry attributes are selected by LokiStack as index labels and as structured metadata, so that I can improve the overall query performance on log streams.
Acceptance Criteria
- The administrator is able to select which resource attributes are indexed as labels, which as structured metadata and which are dropped.
- The administrator is able to configure a global list of resource attributes indexed as labels or stored as structured metadata.
- The administrator is able to override per tenant the global list of resource attributes indexed as labels or stored as structured metadata.
- The administrator is able to merge per tenant resource attributes with global resource attributes indexed as labels.
- The administrator is able to configure global lists of log and scope attributes stored as structured metadata or dropped.
- The administrator is able to configure per tenant lists of log and scope attributes stored as structured metadata or dropped.
Developer Notes:
- The official Loki version supporting the OTLP API in GA is v3.0.0.
- Loki allows only resource attributes to be indexed as labels. Everything else such as log or scope labels can be stored as structured metadata or dropped.