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.

Sign up for GitHub

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

Jump to bottom

[ConfluentKafka] Implement a process span to ease connecting traces #1932

Closed
g7ed6e opened this issue Jun 28, 2024 · 0 comments · Fixed by #1937
Closed

[ConfluentKafka] Implement a process span to ease connecting traces #1932

g7ed6e opened this issue Jun 28, 2024 · 0 comments · Fixed by #1937
Labels
comp:instrumentation.confluentkafka Things related to OpenTelemetry.Instrumentation.ConfluentKafka

Comments

@g7ed6e
Copy link
Contributor

g7ed6e commented Jun 28, 2024 

          > I do still think we could do more to help connect traces when consuming ([#1493 (comment)](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/1493#discussion_r1640199079)) but LGTM that could be done as follow-up work.

@CodeBlanch I missed that comment. I propose to implement it in a follow up PR.

Originally posted by @g7ed6e in #1493 (comment)
@Kielek Kielek added the comp:instrumentation.confluentkafka Things related to OpenTelemetry.Instrumentation.ConfluentKafka label Jul 2, 2024
@g7ed6e g7ed6e mentioned this issue Jul 2, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
comp:instrumentation.confluentkafka Things related to OpenTelemetry.Instrumentation.ConfluentKafka
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a process span to ConfluentKafka instrumentation g7ed6e/opentelemetry-dotnet-contrib
2 participants
@g7ed6e @Kielek