Sidekiq: Stacktrace (or line number) for errors

[sandstrom]

Would it be possible to keep a stacktrace (or at least the line/col which raised the exception) for errors?

Right now it's a bit of guess-work to figure it out.

I know it's possible to grab the error and extract this info (we do this in production), but great benefit with the current admin-UI is that it's simple and convenient.

So extending it with stacktrace/line-number would be in that spirit. ⛵

[mperham]

sidekiq_options backtrace: true

On Sep 13, 2016, at 07:07, sandstrom [email protected] wrote:

Would it be possible to keep a stacktrace (or at least the line/col which raised the exception) for errors?

Right now it's a bit of guess-work to figure it out.

I know it's possible to grab the error and extract this info (we do this in production), but great benefit with the current admin-UI is that it's simple and convenient. So extending it with stacktrace/line-number would be in that spirit. ⛵

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[sandstrom]

@mperham Thanks! 😄

[BartlomiejSkwira]

I have placed this snippet in my config/initializers/sidekiq.rb file:

#print backtraces when exceptions occur
Sidekiq.default_worker_options = { 'backtrace' => true }

Just remembert to restart the server for the initializer to work

The output should look like this: