[
https://issues.apache.org/jira/browse/KAFKA-19727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021492#comment-18021492
]
Apoorv Mittal edited comment on KAFKA-19727 at 9/19/25 7:39 PM:
----------------------------------------------------------------
[~lacey] Thanks for raising it but it's not a bug rather the feature is per
design in KIP-714, i.e. feature default behaviour as `opt-in`.
was (Author: apoorvmittal10):
[~lacey] Thanks for raising it but it's not a bug rather the feature is per
design in KIP-714.
> Make open telemetry object instantiation configurable
> -----------------------------------------------------
>
> Key: KAFKA-19727
> URL: https://issues.apache.org/jira/browse/KAFKA-19727
> Project: Kafka
> Issue Type: Bug
> Components: config
> Affects Versions: 3.7.0, 3.8.0, 3.9.0, 4.0.0
> Reporter: Jonathan Lacefield
> Priority: Major
>
> After the 3.7 release of Kafka, the java client will emit many warning
> messages and more objects deployed due to an open telemetry object
> instantiation (possibly due to KIP-714). It appears the open telemetry
> feature was enabled by default and there's no way for a user to disable it.
> Users receive the INFO message defined [here
> |https://github.com/apache/kafka/blob/3.7.2/clients/src/main/java/org/apache/kafka/common/telemetry/internals/ClientTelemetryReporter.java#L479]
> after activating INFO log level for
> "org.apache.kafka.common.telemetry.internals.ClientTelemetryReporter" class.
> This log line appears lots of times.
> It appears that the occurrence of this info messages shows ClientTelemetry
> objects are being created if the feature is not explicitly disabled. Users
> would like this feature to be opt-in and not enabled by default as it is.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
