Sentry SDKs that work with Epure error tracking

Epure error tracking is compatible with the official Sentry SDKs for errors: @sentry/nextjs, @sentry/node, @sentry/browser, Python sentry-sdk, sentry-go, sentry-ruby, sentry/sentry-laravel, sentry-java, Sentry for .NET and more work after a dsn change. Ingest tests post 102 envelopes from 22 Sentry SDK fixture families, and each is accepted and stored. Epure keeps errors and drops transactions, replays and profiles.

There is no Epure SDK. JS and TS frames are symbolicated with source maps; other languages show raw frames. To switch an existing app, follow switch from Sentry and keep the Sentry SDK.

Which Sentry SDK versions are tested with Epure?

Every row below is a folder under fixtures/sentry/ in the engine repo. The versions are the SDK versions written in each fixture's envelope header. A fixture passes when POST /api/<project-id>/envelope/ returns 202, raw and gzip, and the event's issue appears in the database; the feedback fixtures must also create their feedback rows (ingest_envelope.rs, Epure v0.2.0, checked 6 Nov 2026).

Where a row has two or three distinct versions but more envelopes, the extra envelope is the folder's default envelope.txt, which carries one of the listed versions. "Kept" and "Dropped" come from the envelope parser and the stored-event code, not from per-fixture assertions: a fixture proves the event is accepted and grouped into an issue.

Is Epure compatible with the Sentry SDK for everything?

No. Epure error tracking is compatible with the Sentry SDK for errors, not for every Sentry product. The ingest route answers on the paths the SDK already uses, /api/<project-id>/envelope/ and the older /api/<project-id>/store/, with the public key from the DSN. It stores error events, user feedback and Sentry Crons check-ins. Tracing, session replay, profiling, logs and metrics have no Epure counterpart.

Epure reads each item in an envelope by its type:

An envelope that carries an event next to dropped items still produces the issue. Duplicate SDK event ids are dropped for 7 days, so a retried send with the same id is not counted twice.

What does Epure keep from a Sentry error event?

Epure keeps the fields used to triage an error and drops the rest. From each stored event it keeps the exception chain with stack frames, the most recent breadcrumbs, contexts (browser, OS, runtime), tags, extra, release, environment, the SDK name and version, the request with a short list of safe headers, and an SDK fingerprint if you set one. It drops module lists, debug images and full header sets.

Privacy defaults apply on top: client IP addresses are never stored, and end-user email and username are off unless the project opts in (data and privacy).

Which Sentry SDK options should you change for Epure?

Change dsn and turn off what Epure drops. Set tracesSampleRate to 0 (Python: traces_sample_rate=0.0), remove replayIntegration() and the profiling integration, and set environment to production, staging or local, the three names the v0.2.0 Issues view filters on.

Sentry.init({
  dsn: process.env.SENTRY_DSN, // https://<public-key>@app.epure.sh/<project-id>
  environment: "production",
  tracesSampleRate: 0,
  // no replayIntegration(), no profiling integration
});

sentry_sdk.init(
    dsn=os.environ["SENTRY_DSN"],
    environment="production",
    traces_sample_rate=0.0,
)

Where the DSN lives in each framework, and what to rebuild after changing it: change the Sentry DSN.

Which platforms get readable stack traces in Epure?

JavaScript and TypeScript get original file, function and line when you upload source maps for the event's release; Epure parses source map files up to 32 MiB each, and accepts sentry-cli uploads. Python, Ruby, PHP, Go, .NET and Rust show raw frames, exactly as the SDK sent them. Java obfuscated with ProGuard and every mobile or native platform stay unsymbolicated. Upload steps: source maps.

Which Sentry SDKs have no Epure fixture?

Any Sentry SDK without a row above is untested: for example sentry-native, Unity, Unreal, Godot, sentry-android and sentry-elixir. They speak the same envelope format, but nobody has run them against Epure's tests, and the native ones need symbol files Epure does not read. Before relying on one, send one test error and check the issue, then open an issue on the engine repo with the SDK name and version so it can become a fixture.

How do you check your Sentry SDK works with Epure?

Send one named error from the deployed app and check two things: the request to /api/<project-id>/envelope/ returned 202 Accepted, and an issue appeared under the matching environment.

Sentry.captureException(new Error("Epure SDK check"));
// expected: 202 Accepted, body {"id":"<event-uuid>"}, then one issue

Any other response names its cause: 401 invalid_dsn (wrong key), 404 project_not_found (wrong project number), 403 subscription_inactive (no active Cloud plan). Every code, with its fix, is in event sent but no issue in Epure.

To run the fixture suite yourself on a checkout of the engine, with a local PostgreSQL:

DATABASE_URL=postgres://<user>:<password>@localhost:5432/<db> \
  cargo test -p epure-server --test ingest_envelope

FAQ

Next