See everything one request did, in order
GET /posts is slow. Open its trace and see 23 queries, 20 of them the same select from users, next to the log lines and the mail this request sent. Buggregator draws them on one time scale and points to the N+1 query. On your machine, from your Sentry traces.

The Request tab of GET /posts: 23 queries in 10 ms, 20 of them the same, with the line in PostController that runs them.
One request, one screen
No more jumping between the query log, the log file and the mail catcher to piece one request together.
One lane per kind
Request, Queries, Cache, Logs, Dumps, Errors, HTTP out, Mail, Jobs, Views. Each item sits at the moment it happened.
N+1 hint
When one request runs the same SQL query five times or more, a hint names the query, the count, the time it took and, when the SDK sends it, the file and line.
Summary on top
For example 23 queries · 41 ms, 2 logs · 1 error, 1 mail. Parts with errors are red.
Repeats in one block
Five or more identical items in a lane, under the same parent, are drawn as one block marked ×N.
Logs, mails and HTTP dumps
They join the timeline by trace id. A log, mail or HTTP dump in the list links to its own page.
Also in the API
The trace API returns the N+1 findings as n_plus_one. The events of the same request: /api/events?trace=<id>.
Why is the posts page slow?
The page lists 20 posts with their authors. The hint above the timeline says: 20 identical queries select * from users where id = ?, from PostController.php line 31. Each post loads its author on its own. Add with('user') to the query, reload the page, and the 20 author queries become one.
Setup in 60 seconds
No registration. No account. Start it and point your app at it.
Start Buggregator
Requires Buggregator v2.14.0 or later. The UI and the Sentry endpoint are both on port 8000. 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
Send traces to Buggregator
The page is built from Sentry traces, so your app needs the Sentry SDK with tracing on. That is enough for queries, cache, outgoing calls and jobs.
SENTRY_LARAVEL_DSN=http://sentry@127.0.0.1:8000/1 SENTRY_TRACES_SAMPLE_RATE=1.0 # the file and line of every query, not only of slow ones SENTRY_TRACE_SQL_ORIGIN_THRESHOLD_MS=0
sentry-laravel sends the file and line only for queries slower than this threshold, 100 ms by default. Set it to 0 on your dev machine.
Put logs and mails on the same scale (optional)
Monolog logs, mails and HTTP dumps join the timeline when they carry the request’s trace id. Laravel’s Http:: client adds it to outgoing calls by itself. Logs and mails need a few lines in your app.
use Monolog\LogRecord;
use Sentry\SentrySdk;
$logger->pushProcessor(function (LogRecord $record): LogRecord {
$span = SentrySdk::getCurrentHub()->getSpan();
if ($span !== null) {
$record->extra['trace_id'] = (string) $span->getTraceId();
}
return $record;
});
A Monolog processor that writes the trace id into extra.trace_id.
Open a trace
Open Sentry → Traces and click a trace. The Request tab opens first. Waterfall, Flame graph, Call graph and Sequence are still there.
Built on the Sentry traces you already send
No new package. Logs, mails and HTTP dumps join when they carry the trace id.
Good to know
- Needs Sentry tracing on, for example SENTRY_TRACES_SAMPLE_RATE=1.0.
- Queries count as the same when only their numbers, strings and IN (…) lists differ.
- The file and line show only when the SDK sends them. Queries from lazy-loaded relations such as $post->user often come without them.
- Only Monolog logs, mails and HTTP dumps are linked by trace id. Ray and VarDumper events are not.
- Mails and HTTP dumps stored before the upgrade are not linked.
Ready to try it?
One command to start. No account needed.
Also built into Buggregator