Fresh install
Never used Sentry? Start here.
- 1. Compose up on your host
- 2. Install sentry-rails
- 3. Init with the Epure DSN and verify
RailsError tracking for Rails with sentry-rails
Use this page when Rails should boot Sentry from config/initializers/sentry.rb. Use /integrations/ruby for Sinatra, Sidekiq, and plain Ruby. Add gems sentry-ruby and sentry-rails. Set traces_sample_rate to 0. The captured fixture is sentry-ruby 5.18.0, not a live Rails smoke.
Host up → install SDK → paste DSN (project id from Settings → SDK connection) → confirm a 202.
Start here
From zero, or from Sentry.
Same finish line: sentry-rails pointing at your Epure DSN, first issue in the list.
Already on Sentry
Keep the SDK. Change the DSN.
- 1. Create an Epure project and copy the DSN
- 2. Replace only the dsn string in init
- 3. Set traces/replay/profile rates to 0
Docs for this stack
The fit
Epure is the error tracker for Rails.
Install sentry-rails once. Point the DSN at Epure. No Sentry Cloud account required. Only the open SDK client.
Official SDK, no proprietary agent
Install sentry-rails (or keep it if you already have Sentry). Point dsn at Epure.
Self-host without a broker fleet
Postgres holds issues and events. No Kafka or Redis in the OSS compose. Self-host is a $0 software license; you still run the host. Cloud Pro is $24 and Plus is $79.
Issues you can finish
Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.
What Rails reports
Controller exceptions that stay buried in the log.
sentry-rails hooks the app from the initializer. Grouping uses raw frames. The Ruby page stays Sinatra, Sidekiq, and scripts.
config/initializers/sentry.rb
Sentry.init runs at boot. dsn comes from ENV.fetch("SENTRY_DSN"). traces_sample_rate is 0.0.
Controllers
Unrescued controller exceptions post envelopes after the initializer loads.
sentry-rails middleware
Keep the sentry-rails Railtie. The Ruby gem sentry-ruby stays in the Gemfile beside it.
sentry-ruby 5.18.0
The in-repo fixture is that gem capture. It is not a live Rails smoke.
Raw-frame stacks
No Ruby symbol server. File, method, and line as sentry-ruby sends them.
Install path
Host. SDK. First issue.
New to Sentry or already on it. Same three moves. Official SDK in, DSN pointed at Epure, one test throw.
Run Epure
docker compose up locally (optional `.env` for ports). Register, name a project, copy the DSN from setup or Settings → SDK connection. Self-host is the path that ships today.
Install sentry-rails
Add the official Sentry SDK from your package manager. Epure speaks the Sentry wire, so there is no @epure/* client.
Init and verify
Call Sentry.init with the Epure DSN. Throw once (or captureException). Confirm 202 and an issue in the list.
Wire path
Add both gems. Init in the Rails initializer.
sentry-ruby and sentry-rails. traces_sample_rate is 0. The fixture line is sentry-ruby 5.18.0.
Install sentry-rails
Official Sentry client from the package registry. No @epure/* SDK.
Point dsn at Epure
Paste the project DSN from Settings. Fresh install and Sentry migrants use the same field.
Disable discarded lines
Set traces, replay, and profile sample rates to 0. Epure stores exceptions only.
1bundle add sentry-ruby sentry-railsWhy Epure
Install sentry-rails. Point the DSN. Verify.
Keep the official SDK. Change only the host.
Official SDK, no proprietary agent
Install sentry-rails (or keep it if you already have Sentry). Point dsn at Epure.
Self-host without a broker fleet
Postgres holds issues and events. No Kafka or Redis in the OSS compose. Self-host is a $0 software license; you still run the host. Cloud Pro is $24 and Plus is $79.
Issues you can finish
Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.
Honest scope
Exceptions and stacks. We skip replay, profiling, and transaction APM, and never claim 100% compatibility.
Raw-frame grouping
Grouping uses file, function, and line as the SDK sends them. No ProGuard, dSYM, or NDK.
You own the data path
Self-host keeps stack traces on your Postgres. Cloud soft-samples instead of surprise invoices.
FAQ
Before you paste the Rails DSN.
Do I need an existing Sentry Cloud account?
No. Install sentry-rails from the package registry, create an Epure project, paste the DSN, and capture. You need their open SDK client, never their SaaS. Quickstart.
I already use sentry-rails. Do I rewrite?
No. Leave the SDK. Change only the dsn to your Epure host. Set traces/replay/profile sample rates to 0 so you don’t ship volume Epure discards. Self-host install if you still need compose.
What about transactions, replay, and profiling?
Epure is exception tracking. Transactions are discarded. Replay and profiling items are ignored. Disable those sample rates in init.
How long until I see the first Rails issue?
With Docker warm and a DSN in env, most people land a 202 and an issue the same sitting. Persistence is async, so under normal load an issue appears in well under a second.
Which wire path does Rails use?
Ruby envelope POST /api/{project_id}/envelope/. The captured fixture is sentry-ruby 5.18.0, not a live Rails smoke. This page is the sentry-rails initializer with traces_sample_rate at 0.
How do I verify the first Rails issue?
Raise from a controller after the initializer has booted. Expect HTTP 202, then an issue row. Verify. A rejected DSN: Invalid DSN. A 202 with an empty list: Events not showing. Epure stores exceptions. No session replay, distributed tracing, profiling, or logs.
Point Rails at Epure tonight.
Compose up. Add sentry-ruby and sentry-rails. Init in config/initializers/sentry.rb.
Apache 2.0 · official Sentry SDK · swap DSN