New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Confluent Platform Intergration - Correct Mbean regex stream thread metric #17490
base: master
Are you sure you want to change the base?
fix: Confluent Platform Intergration - Correct Mbean regex stream thread metric #17490
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
Test Results8 files 8 suites 53s ⏱️ Results for commit d07f286. ♻️ This comment has been updated with latest results. |
@jhgilbert thank you for your approve. |
@jhgilbert how may i merge this pr? |
- include: | ||
domain: kafka.streams | ||
bean_regex: kafka\.streams:type=stream-metrics,client-id=.* | ||
bean_regex: kafka\.streams:type=stream-thread-metrics,thread-id=.* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add this entry as new one for this bean regex instead of overwriting the current one? If we overwrite this, it might break some backwards compatibility with at least version 5 of confluent platform:
https://docs.confluent.io/legacy/platform/5.0.0/streams/monitoring.html#:~:text=MBean%3A%20kafka.streams%3Atype%3Dstream%2Dmetrics%2Cthread.client%2Did%3D%5BthreadId%5D
Moving this to a new entry will ensure both legacy and new versions to submit this metric.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@steveny91 Thank you your advice.
Metrics have been added for compatibility up to version 5.4.10.
Please confirm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tlsdnwn55 Thanks for the contribution. I left one comment on the change.
…least version 5 of confluent platform
@steveny91 Could you please confirm? |
@@ -0,0 +1,2 @@ | |||
|
|||
Fix correct Mbean regex stream thread metric(after version 5.5.0 of confluent platform). Previously, because Bean Regex was set to Client metrics, Stream Thread Metrics were not collected. also added one useful attribute for debugging Stream Thread performance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix correct Mbean regex stream thread metric(after version 5.5.0 of confluent platform). Previously, because Bean Regex was set to Client metrics, Stream Thread Metrics were not collected. also added one useful attribute for debugging Stream Thread performance. | |
Add a Bean regex for stream thread metrics for Confluent version >=5.5.0. Previously, Stream Thread Metrics were not collected. Also added one useful attribute for debugging stream thread performance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks I think your suggestion is more appropriate.
Looks good on my end. Thanks for the contribution. I'll get this merged in next week so that it can be released with the next agent (7.55). One last nit is to rename the changelog enty file from |
@steveny91 thank you! |
What does this PR do?
Fixed the JMX Mbean regex to collect stream thread metrics of ksqldb in Confluent Platform.
And added the blocked-time-ns-total metric. (described in confluent docs as being very useful for debugging Kafka Streams application performance)
Motivation
I am maintaining a confluent platform, and while configuring the ksqldb dashboard, I discovered that stream thread metrics were not collected.
Additional Notes
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged