Sidekiq::Shutdown errors are reported but they're normal handled exceptions about dd-trace-rb HOT 3 CLOSED

Hey @Ferdy89, thanks for bringing this up! Sounds like a good suggestion; we'll need to reconcile the Sidekiq error handler with how the Sidekiq tracer works. I'd be happy to take a deeper look at this and get back to you.

from dd-trace-rb.

Took a look into reproducing this issue, and it does indeed flag Sidekiq jobs that are aborted by Sidekiq::Shutdown exceptions as errors.

Good news is that if you'd like these not to report as errors, you can using the "Processing Pipeline" feature, which allows you to modify or filter out spans to customize your application's needs.

Here's a snippet I whipped up that will remove the error status from Sidekiq jobs that fail via shutdown. It preserves the back traces and exception type, but the UI will render their status as "Ok" instead of "Error". Just add it to your Datadog initializer file:

# Unflag Sidekiq jobs that fail with Sidekiq::Shutdown errors
Datadog::Pipeline.before_flush(
  Datadog::Pipeline::SpanProcessor.new do |span|
    if span.name == 'sidekiq.job' && span.get_tag(Datadog::Ext::Errors::TYPE) == 'Sidekiq::Shutdown'
      span.status = 0
    end
  end
)

Wanna give this a shot and let me know if this helps?

from dd-trace-rb.

Closing this given the lack of activity. Please feel free to respond here if you'd like to revisit this issue.

from dd-trace-rb.