Problem
KafkaJS producer and consumer spans do not include messaging.kafka.cluster.id. When the same topic name exists across multiple clusters or environments, there is no way to distinguish which cluster a span came from.
Expected behavior
messaging.kafka.cluster.id (semconv) should be available as an opt-in experimental attribute on KafkaJS producer and consumer spans, disabled by default via the existing captureExperimentalSpanAttributes flag.
Context
Part of a cross-language effort to add this attribute consistently across OTel instrumentations. See opentelemetry-java-instrumentation#18977 for the cross-language tracking issue.
Problem
KafkaJS producer and consumer spans do not include
messaging.kafka.cluster.id. When the same topic name exists across multiple clusters or environments, there is no way to distinguish which cluster a span came from.Expected behavior
messaging.kafka.cluster.id(semconv) should be available as an opt-in experimental attribute on KafkaJS producer and consumer spans, disabled by default via the existingcaptureExperimentalSpanAttributesflag.Context
Part of a cross-language effort to add this attribute consistently across OTel instrumentations. See opentelemetry-java-instrumentation#18977 for the cross-language tracking issue.