[Quarkus/Opentelemetry] Cant drop Kafka Traces

[AchimGrolimund]

Describe the bug

I have a Quarkus application that processes thousands of Kafka events per second. However, I don't want to have a trace/span for every Kafka event.

https://quarkus.io/guides/opentelemetry

how can i disable the creation of traces for Kafka?

i got 4 different ENVS

            - name: OTEL_INSTRUMENTATION_KAFKA_ENABLED
              value: 'false'
            - name: OTEL_INSTRUMENT_MESSAGING
              value: 'false'
            - name: QUARKUS_OTEL_INSTRUMENT_MESSAGING
              value: 'false'
            - name: QUARKUS_OTEL_INSTRUMENTATION_KAFKA_ENABLED
              value: 'false'

The documentation is very unclear, especially when you have part of an agent and part of a library, and then there's the Quarkus library.

Best Achim

Steps to reproduce

Create a Quarkus app that processes/produces many Kafka events and implement the OpenTelemetry library.

Expected behavior

Possibility to prevent instrumentation using ENV for all Kafka events

Actual behavior

Chewing traces per second only for Kafka events

Javaagent or library instrumentation version

quarkus-opentelemetry

Environment

<quarkus.platform.version>3.20.2.redhat-00002</quarkus.platform.version>

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[jaydeluca]

hey @AchimGrolimund have you considered opening an issue with quarkus? That instrumentation is not maintained in this project

The documentation is very unclear, especially when you have part of an agent and part of a library, and then there's the Quarkus library.

As mentioned in this discussion, you should not be using the agent and the quarkus extension together (it's not clear to me whether this is the case here, but just mentioning it).

[laurit]

These environment variables are used to configure the open telemetry java agent, they probably don't work with the quarkus open telemetry extension. You will have to reach out to quarkus community or consult with quarkus documentation for the specifics on how to configure the quarkus open telemetry extension. cc @brunobat

[brunobat]

@AchimGrolimund, the tracing is related with the kafka client extension you are using. OTel tracing for messages is available in the Smallrye Reactive Messaging for Kafka client bundled in the quarkus-messaging-kafka extension.

See: https://quarkus.io/guides/kafka

[github-actions]

This issue has been labeled as stale due to lack of activity and needing author feedback. It will be automatically closed if there is no further activity over the next 7 days.