← All platforms

Resque error tracking

Resque forks a worker. The job fails. Keep the Ruby backtrace after that process is gone, with the Sentry integration and your own Telebugs server.

~/hoofnotes  bundle add sentry-ruby sentry-resque
~/hoofnotes  nvim config/initializers/sentry.rb
require "sentry-ruby"
require "sentry-resque"
Sentry.init do |config|
# Copy the complete Telebugs DSN, key and path included.
config.dsn = "YOUR_TELEBUGS_DSN"
end
~/hoofnotes  RUN_AT_EXIT_HOOKS=1 QUEUE=notes bundle exec rake resque:work

Hang on, I already use Sentry

Keep sentry-resque and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.

What about Resque’s forked workers?

The Resque integration supports reporting from job processes. Its shutdown handling lets queued reports be sent before a child exits; the report then lives in Telebugs.

Can I see my Rails errors here too?

Yes. The Rails integration handles web requests, while the worker integration handles jobs. Both can report to the same Telebugs server.