Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple Trace-ids are generated for Kafka sink connector #12322

Open
jiten686 opened this issue Sep 24, 2024 · 5 comments
Open

Multiple Trace-ids are generated for Kafka sink connector #12322

jiten686 opened this issue Sep 24, 2024 · 5 comments
Assignees
Labels
contribution welcome Request makes sense, maintainers probably won't have time, contribution would be welcome new instrumentation

Comments

@jiten686
Copy link

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

@jiten686 jiten686 added bug Something isn't working needs triage New issue that requires triage labels Sep 24, 2024
@laurit
Copy link
Contributor

laurit commented Sep 24, 2024

@jiten686 is this duplicate of #12261

@laurit laurit added the needs author feedback Waiting for additional feedback from the author label Sep 24, 2024
@jiten686
Copy link
Author

@laurit Not completely. Basically, what I am asking is, a Kafka sink connector send data from a Kafka topic to a MongoDB database. Multiple processes are performed within the connector during a single transaction. However, I am observing multiple trace IDs for each process, instead of a single trace ID being propagated across all processes for the same transaction.

@github-actions github-actions bot removed the needs author feedback Waiting for additional feedback from the author label Sep 24, 2024
@laurit
Copy link
Contributor

laurit commented Sep 25, 2024

Most likely this is going to require a new instrumentation. We'd welcome a contribution for this. Alternatively you may work with the authors of mongo-kafka-connect and have opentelemetry support added there.
To increase the changes of anybody deciding to work on this issue consider providing a minimal application along with any necessary instructions that reproduces your issue.

@laurit laurit added contribution welcome Request makes sense, maintainers probably won't have time, contribution would be welcome new instrumentation and removed bug Something isn't working needs triage New issue that requires triage labels Sep 25, 2024
@vasantteja
Copy link

@laurit If this is open can I take a stab at this?

@vasantteja
Copy link

Folks, I am working on this. I will open a pr once done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution welcome Request makes sense, maintainers probably won't have time, contribution would be welcome new instrumentation
Projects
None yet
Development

No branches or pull requests

3 participants