Epure
.NET.NET · Sentry

Error tracking for .NET.

Add the Sentry NuGet package and set the DSN to your Epure host. ASP.NET Core and hosted-service exceptions land as issues grouped on raw frames.

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

  • Install

    1 SDK

    Install Sentry (.NET). 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 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
  • 3. Init with the Epure DSN and verify

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
The fit

Epure is the error tracker for .NET.

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

  • Official SDK, no proprietary agent

    Install Sentry (.NET) (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 .NET hides

ASP.NET and worker failures that never become a clean ticket.

Epure groups .NET exceptions from web and background hosts. Grouping uses raw frames.

  • ASP.NET Core

    ASP.NET Core

    Keep UseSentry / SentryAspNetCore. Unhandled exceptions still post envelopes after the DSN swap.

  • Minimal APIs

    Workers & HostedService

    Background services share a project DSN or use a dedicated one.

  • .NET workers

    Unhandled exceptions

    SDK hooks at the host level keep working. Only the DSN string changes.

  • Scope & breadcrumbs

    Scope & breadcrumbs

    ConfigureScope data stays on the event for triage in the issue detail.

  • Raw-frame stacks

    Raw-frame stacks

    No .NET symbol server beyond what the SDK embeds. Grouping uses frames as sent.

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 (.NET)

    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

Install the SDK. Point the DSN.

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

  • Install Sentry

    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.

1dotnet add package Sentry
Why Epure

The tracker that fits how you already run .NET.

Check the fit before you paste the DSN.

  • Official SDK, no proprietary agent

    Install Sentry (.NET) (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 .NET DSN.

Do I need an existing Sentry Cloud account?
No. Install Sentry (.NET) 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 (.NET). 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 .NET 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.
Does Epure demangle .NET stacks?
No. There is no Portable PDB symbol server. Grouping uses frames as the Sentry .NET SDK sends them. Keep UseSentry and swap only the DSN host.

Point .NET at Epure tonight.

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

Apache 2.0 · official Sentry SDK · swap DSN