# Ruby on Rails Monitoring & Error Tracking

> Trace ActiveRecord queries and background jobs, catch Sidekiq failures, and resolve exceptions with full stack traces. Free to start.

**URL:** https://sentry.io/for/rails/

---

**Documentation:** [https://docs.sentry.io/platforms/ruby/guides/rails/](https://docs.sentry.io/platforms/ruby/guides/rails/)

## Features

### Rails Performance Monitoring

Quickly identify Rails [performance](/product/tracing/) issues and view full end-to-end distributed trace to see the exact, poor-performing API call and surface any related errors.

### Complete Stack Traces, With Request Context

Take advantage of built-in integrations with Rails, Sidekiq, DelayedJob, and more of your favorite RubyGems. Enable asynchronous reporting so errors are logged quickly in a background job. Filter and group Rails exceptions intuitively to eliminate noise.

### Fill In The Blanks

Expose important events that led to each Rails exception: a string to label where the event took place, message, timestamp. Learn in which version a bug first appeared, merge duplicates, and know if things regress in a future release.

### Your Logs, Next to the Trace

Send your Rails logs to Sentry and query them beside the [trace](/product/tracing/) and the exception. ActiveSupport log output becomes searchable context on the request or background job that failed, rather than something you grep for after the fact.

Learn more about [Logs in Sentry](/product/logs/).

## FAQ

**How do I monitor a Ruby on Rails application?**

Add the [sentry-ruby](/for/ruby/) and `sentry-rails` gems and initialize Sentry in an initializer. You get error monitoring immediately, and enabling tracing gives you distributed traces across your Rails app and the services it calls. Rack middleware is instrumented, and ActiveSupport logs become breadcrumbs on every event.

Add [Profiling](/product/profiling/) for function-level performance data from real users, and [Logs](/product/logs/) to query your Rails logs next to the traces and errors they belong to.

**Does Sentry support Sidekiq and background jobs?**

Yes. Sentry has dedicated integrations for [Sidekiq](/for/sidekiq/) and DelayedJob, so exceptions raised inside background jobs are captured with the job context attached instead of disappearing into a worker log.

For jobs that run on a schedule, [Cron Monitoring](/product/cron-monitoring/) alerts you when a job fails or never runs at all — the silent failures that are hardest to notice.

**Can I send logs to Sentry?**

Yes. Sentry Logs lets you send, view, and query structured logs from your application alongside your errors and traces. Because logs sit next to the error and the trace that produced them, you get the granular context — retries, API failures, internal state — that spans and stack traces alone can miss, without switching tools.

Learn more about [Logs in Sentry](/product/logs/).

**What is Seer, Sentry's AI debugging agent?**

Seer is Sentry's AI debugging agent. It reads the full context Sentry already has — the error, its stack trace, the surrounding trace, logs, and profiles — to find the root cause of an issue and propose a fix. Seer can open a pull request with that fix, hand the work to an external coding agent, or review your PRs before they ship.

Learn more about [Seer](/product/seer/) and [Autofix](/product/seer/autofix/).

**How much does Sentry cost?**

You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our [pricing page](/pricing/).

**How does Sentry impact the performance of my app?**

Sentry doesn't impact a web site's performance.

If you look at the configuration options for when you initialize Sentry in your code, you'll see there's nothing regarding minimizing its impact on your app's performance. This is because our team of SDK engineers already developed Sentry with this in mind.

Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.

Global handlers have almost no impact as well, as they are native APIs provided by the browsers.

---

*Source: [sentry.io/for/rails/](https://sentry.io/for/rails/)*