-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add support for KIP-714 #72
Comments
I guess that should have a wider proposal about how would it work and what would be the benefits. |
In order to implement #55 properly, I realized it made more sense to split the reporter into a client and a server module. #55 and this this issue are server only features so having different modules would simplify the reporter logic. My plan is to open a new proposal for that refactoring (this would change class names and dependencies) and it should cover this issue as well. |
TBH, I'm not sure how KIP-714 relates to splitting the reporter into a client and server modules. You can split that even without involving anything from KIP-714, or? And even if we would want to support KIP-714, the client part would still need to expose the metrics separately as well because not everyone would want to use KIP-714. |
Triaged on 23.1.2025: @mimaison is going to have two proposals for this. One related to the splitting into client and server modules and the other one for supporting KIP-714. |
Since Kafka 3.7.0, with KIP-714 MetricsReporter implementations can also implement the
ClientTelemetry
interface to gather metrics from Kafka clients.The text was updated successfully, but these errors were encountered: