open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Traces are not propagated from kafka connect to mongoDB
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
Describe the bug
I am using Mongo kafka sink connector to send the data from kafka topic to MongoDB. I have set following environment variables on server where my connector is running. I am using Opentelemetry JavaAgent 2.6.0.
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 not able to see the traces from kafka-connector to Mongo DB.
Steps to reproduce
Set the environment variable as per Description.
Run the Mongo kafka sink connect on server.
Expected behavior
Traces should be propagate in a single trace to the database.
Actual behavior
Traces are not propagated in a single trace to the database.
Javaagent or library instrumentation version
Opentelemetry JavaAgent 2.6.0
Environment
JDK:
OS:
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report with the Mongo Kafka sink connector, OpenTelemetry Java Agent 2.6.0, and the listed environment variables. Check the Kafka Connect and MongoDB instrumentation entry points to determine where context propagation stops; done means a connector-to-database operation appears in one trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka, mongodb
- Domain
- backend, distributed-systems, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100