[ https://issues.apache.org/jira/browse/KAFKA-16159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Nee updated KAFKA-16159: ------------------------------- Labels: consumer logging (was: logging) > Prune excessive logging from Telemetry Reporter > ----------------------------------------------- > > Key: KAFKA-16159 > URL: https://issues.apache.org/jira/browse/KAFKA-16159 > Project: Kafka > Issue Type: Task > Components: consumer, log > Reporter: Philip Nee > Assignee: Apoorv Mittal > Priority: Major > Labels: consumer, logging > Fix For: 3.8.0 > > > While running system tests locally, I've noticed excessive logging of the > Telemtry Reporter. This I believe was introduced in KIP-714. > {code:java} > [2024-01-15 09:44:16,911] DEBUG For telemetry state SUBSCRIPTION_NEEDED, > returning the value 224678 ms; the client will wait before submitting the > next GetTelemetrySubscriptions network API request > (org.apache.kafka.common.telemetry.internals.ClientTelemetryReporter) {code} > This is logged several times per ms - Also, given the amount of log being > emitted, can we also check the CPU profile to see if there's a process > running a tight loop? -- This message was sent by Atlassian Jira (v8.20.10#820010)