Multiple Trace-ids are generated for Kafka sink connector #12322
Labels
contribution welcome
Request makes sense, maintainers probably won't have time, contribution would be welcome
new instrumentation
Describe the bug
I am using mongo-kafka-connect-1.6.1-confluence sink connector. I have integrate the opentelemetry java agent with kafka-connect with following environmental variables.
export JAVA_TOOL_OPTIONS=-javaagent:/otel_java_agent/opentelemetry-javaagent.jar
export OTEL_TRACES_EXPORTER=otlp
export OTEL_METRICS_EXPORTER=none
export OTEL_LOGS_EXPORTER=none
export OTEL_EXPORTER_OTLP_PROTOCOL=grpc
export OTEL_PROPAGATORS=tracecontext,baggage
export OTEL_EXPORTER_OTLP_ENDPOINT=http://. ..**
But I am seeing multiple traces are generated in kafka-connect.
What needs to be done so that single transaction will have same trace-id ?
Steps to reproduce
Use Opentelemetry JavaAgent 2.6.0.
Integrate with kafka-connect with above environment variable
Expected behavior
Same trace-id needs to generate for single transaction.
Actual behavior
Multiple trace-ids are generated for single transaction.
Javaagent or library instrumentation version
Opentelemetry JavaAgent 2.6.0 , mongo-kafka-connect-1.6.1-confluence
Environment
JDK:
OS:
Additional context
No response
The text was updated successfully, but these errors were encountered: