REQUEST: New membership for @shashank-reddy-nr

[shashank-reddy-nr]

GitHub Username

@shashank-reddy-nr

Requirements

• I have reviewed the community membership guidelines (https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md)
• I have enabled 2FA on my GitHub account. See https://github.com/settings/security
• I have subscribed to the Slack channel (use https://slack.cncf.io/ to get an invite)
• I am actively contributing to 1 or more OpenTelemetry subprojects
• I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
• I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

• @danielgblanco
• @lmolkova

Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors' confirmation before submitting the request.

List of contributions to the OpenTelemetry project

My contributions center on a cross-language effort to add a stable Kafka cluster.id identifier to OpenTelemetry telemetry, so Kafka producer/consumer/metric signals can be correlated to a specific cluster (disambiguating clusters that reuse identical broker addresses across environments/VPCs).

PRs authored

• open-telemetry/opentelemetry-collector-contrib#48897 — [receiver/kafka_metrics] Add kafka.cluster.id resource attribute (Kafka cluster UUID), auto-discovered from broker metadata. Currently in active review with a maintainer; verified end-to-end across Kafka 0.10.2 → 4.0 (KRaft & ZooKeeper; Apache/Confluent/Strimzi).
• open-telemetry/opentelemetry-java-instrumentation#18978 — feat(kafka): add messaging.kafka.cluster.id from client reflection (includes a Kafka 3.7+ KIP-848 LegacyKafkaConsumer bootstrap-extraction fix).
• open-telemetry/opentelemetry-dotnet-instrumentation#5206 — feat(kafka): add messaging.cluster.id span attribute on Confluent.Kafka producer/consumer spans, with unit + integration tests.
• open-telemetry/opentelemetry-js-contrib#3577 — Kafka cluster.id support for the kafkajs instrumentation.
• open-telemetry/opentelemetry-python-contrib#4727 — Kafka cluster.id support for the Python Kafka instrumentation.
• open-telemetry/semantic-conventions#3819 — proposed defining messaging.cluster.id in the messaging semantic conventions registry (semconv prototype backing the instrumentation PRs above).

Issues authored / responded to

• open-telemetry/opentelemetry-collector-contrib#48892 — [receiver/kafkametrics] feature request for the kafka.cluster.id resource attribute (tracking issue for #48897).
• open-telemetry/opentelemetry-collector-contrib#45280 — bug report: JMX Scraper subprocess crashes at collection intervals ≥ 60s.
• open-telemetry/opentelemetry-java-instrumentation#18977 — feat(kafka): add messaging.cluster.id to producer/consumer spans.
• open-telemetry/opentelemetry-dotnet-instrumentation#5207 — [Kafka] Add messaging.cluster.id span attribute.

[danielgblanco]

I support!

[maryliag]

hey @shashank-reddy-nr, make sure you get 2 sponsors, as requested, before I can send you the invite

[shashank-reddy-nr]

Hi @maryliag, sure thing. I will get another one from the community and let you know once I have it.

[lmolkova]

I support!

[shashank-reddy-nr]

Hi @maryliag I got the 2 sponsors. Can you please proceed?

[maryliag]

invitation sent!