Skip to content

Switch Kafka DSM demo consumers from Python to Java - #40110

Merged
shaina-patel-23 merged 4 commits into
masterfrom
spatel/member-info-consumer-group
Sep 22, 2026
Merged

shaina-patel-23 merged 4 commits into
masterfrom
spatel/member-info-consumer-group

Conversation

@shaina-patel-23

@shaina-patel-23 shaina-patel-23 commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Motivation
Previously we weren't able to see the consumer group members and configuration details for python consumers. This PR fixes that.

Changes

  • Rewrites the Python consumers to Java
  • Added a chaos cluster with a unique CLUSTER_ID (and added kafka3 as a second broker on it) that way its metrics show up under their own cluster:kafka-demo-chaos in the UI instead of getting mashed together with the main cluster.

Testing
Consumer member group

Before After
BeforePR1 AfterPR1
BeforePR2 AfterPR2

Distinguishable clusters
Screenshot 2026-09-22 at 12 51 48 PM

Merge readiness

  • Ready for merge

AI assistance

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
  • 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

Additional notes

@shaina-patel-23 shaina-patel-23 changed the title Spatel/member info consumer group Switch Kafka DSM demo consumers from Python to Java Sep 21, 2026

@chnn chnn left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One nit, looks good though!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(nit) It seems a bit hacky to have a second unique cluster that shares the same cluster ID. All of the metrics reported from this cluster will be indistinguishable from metrics reported from the first cluster, which means the metrics queried in the UI will be some aggregate of the two.

I don't know if this will create problems, maybe it's fine? Alternatively, we could give the second cluster a unique ID and KAFKA_ADVERTISED_LISTENERS. Then (I think) the UI would show the one function cluster, and the offline partition warnings from the second cluster separately.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Applied suggestion, ss is in the PR for the current state. We are now displaying two distinct cluster IDs so they're no longer indistinguishable.

  • Original cluster: cluster:kafka-demo + kafka_cluster_id:Mka3OEVBNTcwNTJENDM2Qg
  • Chaos cluster: cluster:kafka-demo-chaos + kafka_cluster_id:Y2hhb3NDbHVzdGVyMDAwMA

@shaina-patel-23
shaina-patel-23 marked this pull request as ready for review September 22, 2026 16:58
@shaina-patel-23
shaina-patel-23 requested a review from a team as a code owner September 22, 2026 16:58

@OliviaShoup OliviaShoup left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for the PR!

@shaina-patel-23
shaina-patel-23 merged commit 8b1d214 into master Sep 22, 2026
19 of 20 checks passed
@shaina-patel-23
shaina-patel-23 deleted the spatel/member-info-consumer-group branch September 22, 2026 18:57
evazorro pushed a commit that referenced this pull request Sep 24, 2026
* Displaying infra metrics and offline partition health card

* switched consumer groups from py to java

* added a second cluster to distinguish between the original cluster and the choas cluster
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants