One Buggregator for the team, and a feed with only your events
A shared dev server gets busy fast. Filter the feed by machine, environment, user, Monolog channel, level, release or tag, and see only the events you care about. The filters go into the link, so a colleague opens the same view.

+ Add filter lists the fields, which SDKs send each one, and how many values it has.
See only the events you care about
No new setup for most fields: the SDKs already send them.
Your machine only
Five developers and a CI runner send to one server. Pick host = anna-mbp, and the feed shows only Anna’s events.
Six fields and tags
Host, Environment, User, Monolog channel, Level, Release and Sentry or profiler tags. Each value shows how many events have it.
Keep or hide
Enter keeps the matching events, Shift+Enter hides them. The chip shows = or ≠.
Filters in the link
The filters go into the page address, for example ?host=ci-runner-3. Send it to a colleague, and they see the same feed.
New events counted, not mixed in
New events that do not match stay out of the feed. The bar counts them: «N new events arrived and are hidden by this filter».
API and MCP
The same filters on /api/events, values with counts at /api/events/facets, and in the MCP tools events_list and events_facets.
The CI runner floods the shared server
Every test run sends hundreds of errors and logs, and yours get lost between them. Add the filter Host ≠ ci-runner-3, or keep only your machine. Then narrow to Environment = staging and the payments channel. Copy the link and send it to the colleague who asked: they open the same feed.
Setup in 60 seconds
No registration. No account. Start it and point your app at it.
Point everyone at one Buggregator
Requires Buggregator v2.14.0 or later. Most SDKs already send the fields you filter by: Sentry sends the machine, environment, user, release and tags. Events stored before the upgrade are indexed in the background and join the filters as they go.
$ docker run -p 8000:8000 -p 1025:1025 -p 9912:9912 -p 9913:9913 ghcr.io/buggregator/server:latest
Here the ports are open to your network, so the team can reach them. Turn on sign-in (SSO) for the web UI on a server others can reach.
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
Give Monolog logs a machine name (optional)
Monolog sends no machine name by default. Add HostnameProcessor, and your logs get a host you can filter by.
use Monolog\Processor\HostnameProcessor; $logger->pushProcessor(new HostnameProcessor());
Filter the feed
Click + Add filter above the feed, pick a field, then a value. Enter keeps the matching events, Shift+Enter hides them.
# events from one machine curl 'http://127.0.0.1:8000/api/events?host=web-1' # web-1 or web-2, only in staging curl 'http://127.0.0.1:8000/api/events?host=web-1&host=web-2&env=staging' # everything except the CI runner curl 'http://127.0.0.1:8000/api/events?not.host=ci-runner-3' # a Sentry tag, written as name:value curl 'http://127.0.0.1:8000/api/events?tag=feature:checkout'
The same parameter twice means either value; different parameters mean both. not. before a parameter hides the matching events.
Uses what your SDKs already send
A filter finds only events that carry the field.
Good to know
- Emails, SMS, CSP reports and broadcast events have no filter fields, except the trace id of an email.
- Dumps from the command line have no host.
- A hiding filter keeps events that do not have that field at all: not.host=ci-runner-3 keeps logs without a host.
- A tag whose name contains : cannot be filtered. A : in the value is fine.
Ready to try it?
One command to start. No account needed.