Fresh install
Never used Sentry? Start here.
- 1. Run Epure (compose or Cloud)
- 2. Install sentry-php
- 3. Init with the Epure DSN and verify
PHP · sentry-phpError tracking for PHP.
Run composer require sentry/sentry and init with your Epure DSN. Laravel and Symfony exceptions land as issues grouped on raw frames.
Host up → install SDK → paste DSN → confirm a 202.
Install
1 SDK
Install sentry-php. 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-php 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 PHP.
Install sentry-php once. Point the DSN at Epure. No Sentry Cloud account required. Only the open SDK client.
Official SDK, no proprietary agent
Install sentry-php (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 PHP hides
Web and CLI failures that never become tickets.
Epure groups PHP exceptions from HTTP and artisan/cron paths. Grouping uses raw frames.
Laravel / Symfony
Keep official integrations. Unhandled exceptions still post envelopes after the DSN swap.
CLI & workers
Artisan commands and queue workers share a project DSN or use a dedicated one.
Error handlers
Existing set_exception_handler and SDK bridges keep working. The host string is the only edit.
Scope & user
configureScope data stays on the event for triage in the issue detail.
Raw-frame stacks
No PHP symbol server. File, function, and line as sentry-php 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-php
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-php
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.
1composer require sentry/sentryWhy Epure
The tracker that fits how you already run PHP.
Check the fit before you paste the DSN.
Official SDK, no proprietary agent
Install sentry-php (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 PHP DSN.
Do I need an existing Sentry Cloud account?
No. Install sentry-php 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-php. 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 PHP 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 PHP use?
PHP uses POST /api/{project_id}/envelope/. Fixture sentry-php 4.8.0 is captured in-repo; verify ingest in your environment.
Does Epure demangle PHP stacks?
No. There is no PHP symbol server. Grouping uses file, function, and line as sentry-php sends them. Keep official Laravel or Symfony integrations and swap only the DSN.
Point PHP at Epure tonight.
Open the docs, compose up or Cloud, install the SDK, paste the DSN.
Apache 2.0 · official Sentry SDK · swap DSN