Skip to content
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

Kafka Stream consumer metrics were lost in the move away from KafkaConsumerMetrics #21921

Closed
wants to merge 3 commits into from

Conversation

eddumelendez
Copy link
Contributor

See gh-21890

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jun 15, 2020
@snicoll snicoll added for: team-attention An issue we'd like other members of the team to review type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Jun 15, 2020
@snicoll snicoll added this to the 2.4.x milestone Jun 15, 2020
@snicoll
Copy link
Member

snicoll commented Jun 15, 2020

Thanks a lot @eddumelendez. Considering that this was added in Spring Kafka 2.5 and this would complement our native metrics story for Kafka added in 2.3.0, I wonder if merging this in 2.3.x would be the right thing to do. I've flagged this for team attention to get more feedback from the team.

@wilkinsona
Copy link
Member

I think we should wait for 2.4.

@garyrussell
Copy link
Contributor

garyrussell commented Jun 15, 2020

The problem is that the previous (deprecated) Micrometer code scraped JMX MBeans so it would automatically find consumer and producer MBeans, including those registered by Kafka streams.

The issue was reported here - because the binder doesn't use Boot's producer/consumer factories.

When fixing that, I realized the same issue would arise for any Boot app that uses Streams.

So 👍 from me for back-porting to 2.3.x.

@eddumelendez
Copy link
Contributor Author

Should I update the PR and point to 2.3.x?

@wilkinsona
Copy link
Member

wilkinsona commented Jun 17, 2020

I think I understand this now. There's a loss in functionality from 2.2 as the streams-related consumer metrics are gone. What is proposed here will bring them back. We think this is worth fixing in 2.3.

@eddumelendez Thanks for the offer, but there's no need to update the PR unless you particularly want to. We can take care of it as part of merging the change.

@wilkinsona wilkinsona added type: bug A general bug and removed for: team-attention An issue we'd like other members of the team to review type: enhancement A general enhancement labels Jun 17, 2020
@wilkinsona wilkinsona modified the milestones: 2.4.x, 2.3.x Jun 17, 2020
@wilkinsona wilkinsona changed the title Add micrometer support for kafka streams Kafka Stream consumer metrics were lost in the move away from KafkaConsumerMetrics Jun 17, 2020
@snicoll
Copy link
Member

snicoll commented Jun 18, 2020

@garyrussell can you please let us know when you plan to release Spring Kafka 2.5.3? We can switch to snapshot on master as we are releasing 2.4.0-M1 next week.

@snicoll snicoll added the status: waiting-for-feedback We need additional information before we can continue label Jun 18, 2020
@garyrussell
Copy link
Contributor

@snicoll I have scheduled it for next Wednesday.

@spring-projects-issues spring-projects-issues added status: feedback-provided Feedback has been provided and removed status: waiting-for-feedback We need additional information before we can continue labels Jun 18, 2020
@snicoll snicoll removed the status: feedback-provided Feedback has been provided label Jun 19, 2020
Copy link
Member

@snicoll snicoll left a comment

Choose a reason for hiding this comment

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

Thanks for the PR Eddu.

I've made a few suggestions and I've noticed that the Kafka Streams is inconsistent with what we have for producers and consumers. I've added a comment in the related PR in the hope we could harmonize the contract.

@snicoll snicoll added the status: waiting-for-feedback We need additional information before we can continue label Jun 19, 2020
@eddumelendez eddumelendez changed the base branch from master to 2.3.x June 19, 2020 14:24
@eddumelendez
Copy link
Contributor Author

@snicoll changes were applied and now the target branch is 2.3.x. Once the suggestions is applied in spring-kafka I can submit additional changes.

@spring-projects-issues spring-projects-issues added the status: feedback-provided Feedback has been provided label Jun 19, 2020
@spring-projects-issues spring-projects-issues removed the status: waiting-for-feedback We need additional information before we can continue label Jun 19, 2020
@garyrussell
Copy link
Contributor

@eddumelendez
Copy link
Contributor Author

thanks for the notification @garyrussell ! I have introduced new changes in the PR

@wilkinsona wilkinsona removed the status: feedback-provided Feedback has been provided label Jul 1, 2020
@wilkinsona wilkinsona self-assigned this Jul 1, 2020
wilkinsona pushed a commit that referenced this pull request Jul 2, 2020
@wilkinsona wilkinsona closed this in b9bfcdd Jul 2, 2020
@wilkinsona wilkinsona modified the milestones: 2.3.x, 2.3.2 Jul 2, 2020
@wilkinsona
Copy link
Member

Thanks very much, @eddumelendez.

@snicoll
Copy link
Member

snicoll commented Jul 6, 2020

An inner class with an AutoConfiguration suffix seems a bit misleading to me so we should probably rename that, see

wilkinsona added a commit that referenced this pull request Jul 6, 2020
@wilkinsona
Copy link
Member

Well spotted, @snicoll. I've polished that in dfea2f4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants