Fresh install
Never used Sentry? Start here.
- 1. Compose up on your host
- 2. Install sentry/sentry-laravel
- 3. Init with the Epure DSN and verify
LaravelError tracking for Laravel with sentry/sentry-laravel
Use this page when Laravel should read the DSN from config and env. Use /integrations/php for Symfony, Slim, and plain PHP. Require sentry/sentry-laravel and keep sentry/sentry. Set traces_sample_rate to 0. The captured fixture is sentry/sentry 4.8.0, not a live Laravel smoke.
Host up → install SDK → paste DSN (project id from Settings → SDK connection) → confirm a 202.
Start here
From zero, or from Sentry.
Same finish line: sentry/sentry-laravel 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 Laravel.
Install sentry/sentry-laravel once. Point the DSN at Epure. No Sentry Cloud account required. Only the open SDK client.
Official SDK, no proprietary agent
Install sentry/sentry-laravel (or keep it if you already have Sentry). Point dsn at Epure.
Self-host without a broker fleet
Postgres holds issues and events. No Kafka or Redis in the OSS compose. Self-host is a $0 software license; you still run the host. Cloud Pro is $24 and Plus is $79.
Issues you can finish
Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.
What Laravel reports
HTTP and queue failures after config is loaded.
The Laravel package reads config. Grouping uses raw frames. The PHP page stays sentry/sentry init for other frameworks.
config/sentry.php
dsn reads SENTRY_DSN. traces_sample_rate stays 0.0 so discarded transaction volume stays off.
Exception handler
Unhandled HTTP exceptions still post after the DSN points at Epure. Keep sentry/sentry installed.
Queue workers
queue:work boots the same config. A worker that never loads it will not send.
sentry/sentry 4.8.0
The in-repo fixture is that PHP SDK capture. It is not a live Laravel smoke.
Raw-frame stacks
No PHP symbol server. File, function, and line as the SDK 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). Register, name a project, copy the DSN from setup or Settings → SDK connection. Self-host is the path that ships today.
Install sentry/sentry-laravel
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
Require the Laravel package. Set the env DSN.
sentry/sentry-laravel stays on top of sentry/sentry. Config points dsn at SENTRY_DSN. traces_sample_rate is 0.
Install sentry/sentry-laravel
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/sentry-laravelWhy Epure
Install sentry/sentry-laravel. Point the DSN. Verify.
Keep the official SDK. Change only the host.
Official SDK, no proprietary agent
Install sentry/sentry-laravel (or keep it if you already have Sentry). Point dsn at Epure.
Self-host without a broker fleet
Postgres holds issues and events. No Kafka or Redis in the OSS compose. Self-host is a $0 software license; you still run the host. Cloud Pro is $24 and Plus is $79.
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 Laravel DSN.
Do I need an existing Sentry Cloud account?
No. Install sentry/sentry-laravel 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/sentry-laravel. 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 Laravel 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 Laravel use?
PHP envelope POST /api/{project_id}/envelope/. The captured fixture is sentry/sentry 4.8.0, not a live Laravel smoke. Keep sentry/sentry. This page is sentry/sentry-laravel config and SENTRY_DSN.
How do I verify the first Laravel issue?
Throw from a route after config is loaded. Expect HTTP 202, then an issue row. Verify. A rejected DSN: Invalid DSN. A 202 with an empty list: Events not showing. Epure stores exceptions. No session replay, distributed tracing, profiling, or logs.
Point Laravel at Epure tonight.
Compose up. Require sentry/sentry-laravel. Set SENTRY_DSN.
Apache 2.0 · official Sentry SDK · swap DSN