32b688e785
Customers often have Sidekiq jobs that failed without much context. Without Sentry, there's no way to tell where these exceptions were hit. Adding in additional lines adds a bit more Redis storage overhead. This commit adds in backtrace logging for workers that delete groups/projects and import/export projects. Closes #27626
8 lines
186 B
Ruby
8 lines
186 B
Ruby
# Concern for enabling a few lines of exception backtraces in Sidekiq
|
|
module ExceptionBacktrace
|
|
extend ActiveSupport::Concern
|
|
|
|
included do
|
|
sidekiq_options backtrace: 5
|
|
end
|
|
end
|