Epure
GitHub
RubyRuby · sentry-ruby

Error tracking for Ruby.

Install sentry-ruby and init with your Epure DSN. Rails and Sidekiq exceptions land as issues, and sentry-rails integrations keep working.

Install guideOpen GitHub

Host up → install SDK → paste DSN → confirm a 202.

  • Install

    1 SDK

    Install sentry-ruby. Point dsn at Epure.

  • Protocol

    envelope

    Official Sentry wire. Exceptions persist; transactions discarded.

  • Setup

    < 10 min

    Host up → DSN → first issue the same sitting.

  • Cost

    0 seats

    Self-host is unlimited seats. Hardware bounds volume.

Start here

From zero, or from Sentry.

Same finish line: sentry-ruby pointing at your Epure DSN, first issue in the list.

Fresh install

Never used Sentry? Start here.

  • 1. Run Epure (compose or Cloud)
  • 2. Install sentry-ruby
  • 3. Init with the Epure DSN and verify
Self-host installQuickstart

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
Platform guideVerify

Docs for this stack

The fit

Epure is the error tracker for Ruby.

Install sentry-ruby once. Point the DSN at Epure. No Sentry Cloud account required. Only the open SDK client.

  • Official SDK, no proprietary agent

    Install sentry-ruby (or keep it if you already have Sentry). Point dsn at Epure.

  • Two containers, no cluster

    Rust binary plus PostgreSQL 16, self-hosted under 200 MB. Cloud runs the same path at $24.

  • Issues you can finish

    Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.

What Ruby hides

Rails and job failures that bury the stack.

Epure groups Ruby exceptions from controllers and workers. Grouping uses raw frames.

  • Rails

    Rails controllers

    Keep sentry-rails integrations. Unrescued exceptions still post envelopes to the new host.

  • Sinatra

    Background jobs

    Sidekiq and Active Job failures land as issues beside your web app or in a separate project.

  • Sidekiq

    Rack middleware

    Existing middleware stays. Only the DSN string in Sentry.init changes.

  • plain Ruby

    User & tags

    set_user and set_tags from the SDK remain on the event for triage.

  • Raw-frame stacks

    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), or open Cloud. Register, name a project, copy the DSN from setup or Settings → SDK connection.

  • Install sentry-ruby

    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.

Platform docsVerify checklist
Wire path

Install the SDK. Point the DSN.

Fresh install or DSN swap: same init shape. Disable product lines Epure discards.

  • Install sentry-ruby

    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.

1gem install sentry-ruby
Why Epure

The tracker that fits how you already run Ruby.

Check the fit before you paste the DSN.

  • Official SDK, no proprietary agent

    Install sentry-ruby (or keep it if you already have Sentry). Point dsn at Epure.

  • Two containers, no cluster

    Rust binary plus PostgreSQL 16, self-hosted under 200 MB. Cloud runs the same path at $24.

  • 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 Ruby DSN.

Do I need an existing Sentry Cloud account?
No. Install sentry-ruby 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-ruby. 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 Ruby 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 Ruby use?
Ruby uses POST /api/{project_id}/envelope/. Fixture sentry-ruby 5.18.0 is captured in-repo; verify ingest in your environment.
Does Epure demangle Ruby stacks?
No. Symbolication is JS/TS sourcemaps only. Ruby issues group on file, method, and line as sentry-ruby sends them. Sidekiq failures use the same DSN unless you split projects.

Point Ruby at Epure tonight.

Open the docs, compose up or Cloud, install the SDK, paste the DSN.

Install guideOpen GitHub

Apache 2.0 · official Sentry SDK · swap DSN