Everything your Sentry SDK sends, on your machine
Your app already has the Sentry SDK. Change the DSN, and Buggregator shows its errors, traces, logs and metrics on your computer — each in its own tab, linked by trace. No Sentry account, no data leaving your machine.
- http.serverGET /orders/42240ms
- db.querySELECT * FROM orders WHERE id = ?36ms
- cache.getorders:42:items3ms
- http.clientPOST api.payments.test/chargeserror158ms
- db.queryUPDATE orders SET status = ?12ms
One request as a trace: database, cache and HTTP calls on a timeline, with the failing call marked. Example data.
Four kinds of data, one place
Each kind has its own tab for the project and period you pick. New data shows up without a reload.
Errors with full context
Stack trace frame by frame, breadcrumbs, request, tags, device, modules. Show them one by one, or grouped by type with a count. Click a frame to open it in your IDE.
Traces as a waterfall
Every span of a request on a timeline: database queries, cache, HTTP calls, queues — each marked by type. The bar shows how long it took; failed spans are tagged.
Service map
Which service calls which database, cache or API, with request counts and average time. Links turn amber or red when calls fail. Built from the last hour of traces.
Sentry logs
Structured logs from the SDK, filtered by level. Open a line to see its attributes; jump to its trace.
Sentry metrics
Counters, gauges and distributions as your code sends them, with unit and attributes. Filter by type or by part of the name.
Linked by trace
An error shows its trace in a small waterfall; a trace lists the errors that happened in it; logs and metrics link to their trace.
Setup in 60 seconds
No registration. No account. Start it and point your app at it.
Start Buggregator
Buggregator takes Sentry data on port 8000, next to the web UI. One file, about 40 MB, installed with one command. Prefer containers? Use the Docker tab.
$ curl -fsSL https://raw.githubusercontent.com/buggregator/server/master/scripts/install.sh | sh $ HTTP_ADDR=127.0.0.1:8000 \ SMTP_ADDR=127.0.0.1:1025 \ VAR_DUMPER_ADDR=127.0.0.1:9912 \ MONOLOG_ADDR=127.0.0.1:9913 \ PROXY_ADDR=127.0.0.1:8080 \ ~/.local/bin/buggregator
The script picks the file for your CPU: Intel/AMD or ARM.
One file for Linux, macOS and Windows, about 40 MB. Nothing else to install.
Runs on Windows, macOS and Linux, on Intel/AMD and ARM.
Prefer not to do it yourself? Your AI agent can set Buggregator up for you →
Point your SDK at Buggregator
One line in your config. Put a project name in the DSN to keep each app’s data apart.
# .env SENTRY_LARAVEL_DSN=http://sentry@127.0.0.1:8000/my-app
Turn on what you want to see
Errors arrive as soon as the DSN is set. Traces, logs and metrics are SDK features: switch them on in your app.
\Sentry\init([
'dsn' => 'http://sentry@127.0.0.1:8000/my-app',
'traces_sample_rate' => 1.0, // send every trace while you develop
]);
Laravel: SENTRY_TRACES_SAMPLE_RATE=1.0 in .env.
Trigger an error — follow it into the trace
Throw an exception in a request. Buggregator shows it with the stack trace and context, and a small waterfall of the request it happened in. Open the full trace to see every query and call around it.
Built on the Sentry SDK format
Buggregator reads what Sentry SDKs send: errors, traces, logs and metrics. We test it with the Sentry PHP SDK (versions 2.5, 3.22 and 4.x). Other SDKs send the same format; if one doesn’t show up, tell us.
Your SDK doesn’t show up? Tell us on GitHub →
What it leaves out
Session replays, profiles, cron check-ins, release health sessions and attachments are not kept. For PHP profiling, use the Profiler (XHProf) page.
Ready to try it?
One command to start. No account needed.
Also built into Buggregator