Integration Options

Learn about configuring integrations.

rails.report_rescued_exceptions

Rails catches exceptions in the ActionDispatch::ShowExceptions or ActionDispatch::DebugExceptions middlewares, depending on the environment. By default, Sentry will report exceptions even when they are rescued by these middlewares.

You can disable this by setting it to false:

Copied
config.rails.report_rescued_exceptions

rails.skippable_job_adapters

If you don't want to report events from a certain ActiveJob adapter, or you already have a better setup for it, you can use this option to skip ActiveJob reporting on that adapter.

Copied
config.rails.skippable_job_adapters = ["ActiveJob::QueueAdapters::MyAdapter"]

rails.tracing_subscribers

Tracing subscribers are responsible for capturing tracing spans from Rails instrumentation. The default subscribers are:

  • Sentry::Rails::Tracing::ActionControllerSubscriber
  • Sentry::Rails::Tracing::ActionViewSubscriber
  • Sentry::Rails::Tracing::ActiveRecordSubscriber
  • Sentry::Rails::Tracing::ActiveStorageSubscriber
Copied
# you can add a new subscriber
config.rails.tracing_subscribers << MySubscriber
# or replace the set completely
config.rails.tracing_subscribers = [MySubscriber]

delayed_job.report_after_job_retries

sentry-delayed_job captures exceptions whenever they occur in a job execution. You can make it wait until the retry is exhausted. Default is false.

Copied
config.delayed_job.report_after_job_retries = true

sidekiq.report_after_job_retries

sentry-sidekiq captures exceptions whenever they occur in a job execution. You can make it wait until the retry is exhausted. Default is false.

Copied
config.sidekiq.report_after_job_retries = true
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").