Laravel error tracking, one line of .env away.
Bugtail is a Laravel application built by people who ship Laravel applications, and it speaks the Sentry envelope protocol. Change SENTRY_LARAVEL_DSN, deploy, and the package you already have reports here instead.
Nothing to install, nothing to rewrite
Keep sentry/sentry-laravel exactly as it is. The DSN points at our ingest host, the key identifies your collector, and every feature of that package keeps working: the exception handler, the queue and job context, the command context, the release and environment, the breadcrumbs, the performance instrumentation.
If you are not using it yet, install it as the Sentry documentation describes and paste our DSN instead of theirs. There is no Bugtail package to depend on, which is deliberate: a monitoring vendor that needs its own SDK in your composer.json is a vendor you cannot leave in an afternoon.
Queues and jobs
A failing job is an issue with the job class, the queue, the attempt and the payload context.
Octane and Horizon
Long-running workers report the same way, and Horizon metrics can come in over OTLP.
Artisan commands
A command that throws at four in the morning is an issue with the command line that caused it.
Log channel
Ship your Laravel log to the same place as your errors, and alert on a line.
Written in the same stack it watches
Bugtail runs on Laravel with a database per organisation, so the isolation between customers is the same boundary you would build yourself if you had to answer for it. That is not a feature you use; it is the reason the answers on the security page are specific rather than reassuring.
Questions people actually ask
Do I need a Bugtail package in composer.json?
No, and that is on purpose. You use the official Sentry SDK or an OpenTelemetry exporter. Leaving is changing a DSN back.
Does performance instrumentation work?
Yes. The transactions and spans the Sentry SDK produces are read, aggregated by shape and charted. Note that Sentry sends transaction timestamps as fractional seconds; we keep the fraction, which is why durations under a second are not all reported as one second.
Fourteen days of Team, without a card.
Sign up with your work address, prove your domain with one DNS record, and paste a DSN. The first stack trace usually arrives before the coffee does.
No card. The trial ends by itself and drops to Free; nothing is charged unless you choose a plan.
