Story

As a user of ClusterLogForwarder,
I want releases of Logging to attach the "OTel semantics" stream labels to logs output using the LokiStack sink
so that I can use both the ViaQ and the OTel stream labels to query for logs.

Acceptance Criteria

• Verify ingested logs include the following stream labels:

openshift_log_type (same value as log_type)
k8s_namespace_name (same value as kubernetes_namespace_name)
k8s_pod_name       (same value as kubernetes_pod_name)
k8s_container_name (same value as kubernetes_container_name)
k8s_node_name      (same value as kubernetes_host)

• Verify logs are returned in the console UI without error using any of the drop-down controls
• Make sure that customers having a custom LabelKeys configuration will only get the compatibility labels matching their set of "ViaQ labels".

Notes

Logging 6.1 has introduced an alternative data model ("Otel") to be sent to OTLP capable receivers, including our own LokiStack-based storage. The new data model is following the OTel Semantic Conventions for naming the attributes and so uses a different set of "attributes" for the metadata identifying a stream of logs ("stream labels").

Because these stream labels are used by our own log visualization tool, a compatibility layer was built into the new data model, so that it also emits the old attribute names, so that the visualization can be used unmodified with the new data model.

This story proposes to do the same compatibility, but in the other direction, adding the new attributes to the old data-model, so that a query searching for either set of attributes will return both old and new data (LogQL does not have an "or" operator in the stream-label selector).

The change should enable customers to query across both data-models with a single query, allowing easy migration from the old data model to the new one. For this to work properly, this change needs to be backported to all maintained releases of Logging.