Fresh install
Never used Sentry? Start here.
- 1. Run Epure (compose or Cloud)
- 2. Install @sentry/node
- 3. Init with the Epure DSN and verify
Node.js · @sentry/nodeError tracking for Node.js.
Install @sentry/node and set SENTRY_DSN to your Epure host. Process exceptions and unhandled rejections group as issues you can resolve once.
Host up → install SDK → paste DSN → confirm a 202.
Install
1 SDK
Install @sentry/node. 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/node 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 Node.js.
Install @sentry/node once. Point the DSN at Epure. No Sentry Cloud account required. Only the open SDK client.
Official SDK, no proprietary agent
Install @sentry/node (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 Node hides
Server failures that never hit your logs cleanly.
Epure groups Node exceptions from HTTP handlers, workers, and uncaughtException paths into issues you can finish.
Uncaught exceptions
Process-level throws land as one issue per fingerprint instead of a flood of identical log lines.
Unhandled rejections
Promise failures from async routes and jobs land with the stack the worker actually threw.
HTTP handlers
Express, Fastify, and raw http keep posting envelopes through captureException or auto-instrumentation.
Background jobs
Queue consumers and cron scripts share the same project DSN as your API.
Minified / bundled stacks
Upload JS/TS maps via release files when you ship compiled Node bundles.
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/node
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/node
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.
1npm install @sentry/node@7.120.0Why Epure
The tracker that fits how you already run Node.
Check the fit before you paste the DSN.
Official SDK, no proprietary agent
Install @sentry/node (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.
Readable JS/TS stacks
Upload sourcemaps via release files. Local frames stay useful after minify.
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 Node.js DSN.
Do I need an existing Sentry Cloud account?
No. Install @sentry/node 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/node. 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 Node 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 Node use?
Node uses POST /api/{project_id}/envelope/. Fixture @sentry/node 7.120.0 is parse-tested; treat newer majors as verify-in-your-env until CI expands.
Does this work with ESM and CommonJS?
Yes. Import or require @sentry/node the way your service already does. Init as early as possible, then load the rest of the app. Point dsn at Epure. Verify with an uncaught throw in a route you control.
Can bundled Node stacks demangle?
If you compile TypeScript or bundle server code, upload JS/TS sourcemaps via release files. Epure does not demangle other languages. Native addons stay on raw frames.
Point Node at Epure tonight.
Open the docs, compose up or Cloud, install the SDK, paste the DSN.
Apache 2.0 · official Sentry SDK · swap DSN