Proposal: Define mapping from k8s well-known labels to semconv

[smithclay]

Many OpenTelemetry users run their applications in Kubernetes, where it is useful to use a collector processor like k8sattributes to enrich metrics, spans, or logs with k8s metadata like pod name.

The k8sattributes processor also supports enriching metrics, logs, and spans with resource attributes based on Kubernetes labels, including Well Known Labels. It would be helpful to OpenTelemetry users what the recommended best practice is for mapping well-known labels to OpenTelemetry resource attributes.

Two of the most obvious candidates (but open for feedback), are:

• app.kubernetes.io/name -> service.name
• app.kubernetes.io/version -> service.version

To configure k8sattributes to apply these rules, the collector YAML looks like this: https://github.com/lightstep/otel-collector-charts/blob/main/charts/otel-cloud-stack/values.yaml#L166-L168

It seems like these recommendations could (should?) live as an section in this doc: https://opentelemetry.io/docs/specs/otel/resource/semantic_conventions/k8s/

[smithclay]

cc @dmitryax

[arminru]

To configure k8sattributes to apply these rules, the collector YAML looks like this.

@smithclay The "like this" link does not work (any longer)

[smithclay]

To configure k8sattributes to apply these rules, the collector YAML looks like this.

@smithclay The "like this" link does not work (any longer)

Updated here: https://github.com/lightstep/otel-collector-charts/blob/main/charts/otel-cloud-stack/values.yaml#L166-L168 -- thank you!

[joaopgrassi]

This was closed by mistake by the stale bot. Re-opening