Resource/Span attributes collision possible due to default K8s processor behavior

[bixu]

The behavior of this default can have surprising unwanted consequences.

Example:

• A team adds the name label to a k8s Pod
• Backends that don't differentiate between Resource and Span attributes can display traces such that each span shows the k8s pod name as the name of the span

Proposal:

Consider some namespacing when this default is enabled. For example, k8s.pod.label.<label value>.

[TylerHelmuth]

@bixu the semantic conventions do specify a namespacing. This feature was added before that and we are not going to update it until the k8s semantic conventions are stabilized, to minimize the amount to times we need to do a breaking change.

If you need some namespacing I suggest not using the .Values.preset.kubernetesAttributes.extractAllPodLabels field and instead configure the extraction manually:

  k8sattributes:
    extract:
      labels:
        - tag_name: k8s.pod.label.$$1
          key_regex: (.*)
          from: pod

[bixu]

Thanks for the context, we're fine with explicitly configuring this until the semconv settles.

Should we keep the issue for tracking this until then? If not, I'm happy to close.

[TylerHelmuth]

I think closing is fine, we'll have a specific semconv issue for tracking that work