How to Point the Official Sentry SDK at a Self-Hosted Ingest Using DSN Only
Developers can connect the official Sentry SDK — either @sentry/browser or @sentry/node — to a self-hosted ingest server by changing only the DSN, without forking the SDK. The setup requires just two Docker containers, running the app and Postgres 16, cloned from the public epure repository via docker compose up. A successful configuration is confirmed when a GET request to the /health endpoint returns HTTP 200 with a status-ok body, and a captured exception triggers an HTTP 202 response from the ingest server. Unused features such as session replay, distributed tracing, and profiling should have their sample rates set to zero, as the self-hosted host is scoped to exception ingestion only. Once an exception is captured, developers can verify end-to-end wiring by checking the Issues dashboard for an unresolved error entry matching the configured environment.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in