You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We noticed that when a span with the karafka.consume operation encounters an error, it is not propagated to the parent span, like in the screenshot below. We correctly see one operation per Kafka message but the parent span with the worker.process operation looks like no error was detected.
For comparison, this is how the same error used to appear with the integration provided by Karafka:
Uh oh!
There was an error while loading. Please reload this page.
Tracer Version(s)
2.15.0
Ruby Version(s)
ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +PRISM [aarch64-linux]
Relevent Library and Version(s)
No response
Bug Report
We recently upgraded the datadog gem to version 2.15.0 and switched from the Datadog integration provided by Karafka to the one provided by the gem.
We noticed that when a span with the
karafka.consume
operation encounters an error, it is not propagated to the parent span, like in the screenshot below. We correctly see one operation per Kafka message but the parent span with theworker.process
operation looks like no error was detected.For comparison, this is how the same error used to appear with the integration provided by Karafka:
Reproduction Code
No response
Configuration Block
Error Logs
No response
Operating System
No response
How does Datadog help you?
No response
The text was updated successfully, but these errors were encountered: