Skip to content

KAFKA-19185: add logs #19538

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

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from
Open

Conversation

aliehsaeedii
Copy link
Contributor

This PR aims at enhancing logging in Consumer request/response as follows:

  • Logging when a FETCH request is generated, including the correlation ID.
  • Logging the response received before any processing

@github-actions github-actions bot added triage PRs from the community consumer clients small Small PRs labels Apr 22, 2025
Copy link
Contributor

@kirktrue kirktrue 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 @aliehsaeedii!

NetworkClient's request and response handlers log messages with the API key (i.e. FETCH) and the correlation ID. Admittedly all requests and responses are logged, so it would require some filtering. Logging this information at INFO level would be very noisy, IMO.

@@ -131,6 +131,7 @@ public RequestFuture<ClientResponse> send(Node node,
ClientRequest clientRequest = client.newClientRequest(node.idString(), requestBuilder, now, true,
requestTimeoutMs, completionHandler);
unsent.put(node, clientRequest);
log.info("Generated FETCH with correlation id {}.", clientRequest.correlationId());
Copy link
Member

Choose a reason for hiding this comment

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

Logging every request at INFO level, does sound very chatty. I would believe that per-request logging would even be too chatty for DEBUG, and we should make it TRACE instead?

@github-actions github-actions bot removed the triage PRs from the community label Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants