Skip to content

Feature/kafka cluster#4727

Open
shashank-reddy-nr wants to merge 1 commit into
open-telemetry:mainfrom
shashank-reddy-nr:feature/kafka-cluster-id
Open

Feature/kafka cluster#4727
shashank-reddy-nr wants to merge 1 commit into
open-telemetry:mainfrom
shashank-reddy-nr:feature/kafka-cluster-id

Conversation

@shashank-reddy-nr

Copy link
Copy Markdown

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A

Does This PR Require a Core Repo Change?

  • Yes. - Link to PR:
  • No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added
  • Documentation has been updated

@linux-foundation-easycla

linux-foundation-easycla Bot commented Jun 22, 2026

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: shashank-reddy-nr / name: Pulipelly Shashank Reddy (3760932)

When a service connects to multiple Kafka clusters, or when the same topic name
exists across environments, Kafka spans carry no information about which cluster
a message came from. messaging.cluster.id is defined in the OTel messaging
semantic conventions for Kafka but was not previously set by this instrumentation.

Adds messaging.cluster.id as a span attribute on producer and consumer spans for
Confluent.Kafka (≥2.0.0). A one-time background AdminClient.DescribeClusterAsync()
call is made per unique bootstrap-servers string; security config (SASL/SSL) is
forwarded so authenticated clusters are supported. The attribute is omitted on
older library versions or if resolution has not yet completed — no overhead on
the hot path.

Assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com>
@shashank-reddy-nr shashank-reddy-nr force-pushed the feature/kafka-cluster-id branch from 937e539 to 3760932 Compare June 22, 2026 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant