Laravel Error Tracking for Queues, Jobs, APIs

Your own Laravel error tracker, hosted on your infrastructure

Laravel production errors do not only happen in controllers. A failed queued job, scheduled command, notification, event listener, webhook, API route, or Eloquent query can affect customers long before someone notices a log line.

Telebugs gives those errors a focused place to land. It runs on your server, accepts events from the official Sentry Laravel SDK, and keeps the familiar SDK workflow without sending your error data to a hosted error-tracking SaaS.

You keep the parts that matter for debugging: grouped issues, detailed backtraces, breadcrumbs, releases, notifications, notes, and retention controls.

What Telebugs gives Laravel teams

Telebugs keeps error tracking simple and practical. It gives Laravel teams the core workflow: readable reports, grouping, releases, notifications, notes, retention controls, and ownership of the server.

It is also predictable to budget for. Just $299.99 once.

Just compare the pricing for yourself

That makes it a practical fit for Laravel apps that can produce errors from many places at once: HTTP requests, validation paths, Eloquent models, jobs, queues, scheduled commands, event listeners, webhooks, and APIs.

Smart Laravel error grouping

Telebugs groups similar Laravel errors automatically. This cuts down on duplicate noise when one broken route, queue worker, Eloquent query, or deploy regression affects many users. See the error grouping guide for details, including custom grouping and fingerprinting rules.

Notifications for real user impact

Send Laravel production errors to email, push, Slack, Discord, Microsoft Teams, or a webhook. Rules help you separate urgent production failures from expected validation noise, transient provider errors, or low-priority background jobs.

Use notification rules to route HTTP exceptions, failed jobs, webhook errors, and deploy regressions to the right people. Full details live in the notifications and rules guide.

Detailed backtraces and breadcrumbs

Telebugs captures detailed backtraces for Laravel exceptions so you can see the controller, job, command, listener, service class, or model path involved in the failure. Breadcrumbs can show the lead-up: HTTP requests, queue jobs, middleware, external calls, logs, and custom app context.

Where Laravel production errors hide

Laravel apps often have several execution paths beyond web requests. A useful error tracker helps you understand which path failed and whether the impact is user-facing, operational, or isolated to a background workflow.

• HTTP and API errors from routes, controllers, middleware, validation paths, webhooks, and third-party integrations.
• Database and model errors from Eloquent queries, missing records, migrations, transactions, and unexpected data shapes.
• Queue and worker errors from jobs, listeners, notifications, retries, failed batches, and Horizon-style worker workflows.
• Scheduled and CLI errors from Artisan commands, cron jobs, imports, reports, and maintenance scripts.

Telebugs helps connect those events to grouped issues, notification rules, and the release or deploy that introduced a regression.

Laravel error context worth capturing

The stack trace tells you where Laravel raised the exception. The surrounding context tells you whether it came from a customer request, a background job, a queue retry, a webhook, or a scheduled command.

• Release and environment so production, staging, preview deploys, and canaries stay separated.
• Route, controller, job, queue, and command tags so recurring failures are easier to triage.
• User, account, or tenant identifiers when they help support and engineering understand impact.
• Queue metadata such as job names, retry counts, batch IDs, and worker context.
• Breadcrumbs for database queries, HTTP calls, logs, queue dispatches, and custom app events.

Because Telebugs is self-hosted, you can capture useful debugging context while keeping control of privacy, retention, and sensitive-data scrubbing.

Setup that is friendly to Laravel teams

Getting Telebugs running for Laravel errors does not require a large observability project. Install Telebugs on your server, create a project, copy the DSN, and initialize the Sentry Laravel SDK in your app. The installation guide walks through the server side.

Once the server is running, Laravel errors start flowing through the same SDK workflow many PHP teams already know from Sentry.

How to integrate Telebugs with Laravel

Telebugs works with the official Sentry Laravel package. The main difference from Sentry is the DSN.

Install the Sentry Laravel package with Composer:

composer require sentry/sentry-laravel

Add your Telebugs DSN to your .env file. Replace your-telebugs-dsn with the DSN provided in your Telebugs dashboard:

SENTRY_LARAVEL_DSN=your-telebugs-dsn

Configure the Sentry integration in your Laravel application. In current Laravel applications, that commonly means wiring the Sentry exception handler in bootstrap/app.php:

withRouting(
        web: __DIR__.'/../routes/web.php',
        commands: __DIR__.'/../routes/console.php',
        health: '/up',
    )
    ->withMiddleware(function (Middleware $middleware) {
        //
    })
    ->withExceptions(function (Exceptions $exceptions) {
        Integration::handles($exceptions);
    })
    ->create();

Publish the Sentry configuration to set up the DSN and other options:

php artisan sentry:publish --dsn=your-telebugs-dsn

Verify the integration by triggering a test error. You can use the following command to send a test event to Telebugs:

php artisan sentry:test

Events captured by the official Sentry Laravel SDK are sent to Telebugs, where they can be grouped, searched, assigned, annotated, and linked to releases.

Check the Sentry Laravel docs for more details if you need them. For the full picture across SDKs and languages, see our Sentry SDK compatible page.

AI-friendly Laravel debugging with MCP

Telebugs supports MCP, which makes it easier for AI tools that speak the Model Context Protocol to inspect error data without you copying stack traces by hand. For Laravel teams, that can mean faster investigation of exception backtraces, breadcrumbs, queue metadata, release context, and affected routes.

The useful version of AI debugging is quiet and controlled: your source of truth stays in Telebugs, your sensitive data rules still apply, and an assistant can help reason about a production issue from the same structured context your team already captured. See MCP error tracking for the broader workflow.

Frequently asked questions about Telebugs and Laravel

Can I use Telebugs with my Laravel version?

Telebugs is compatible with the Laravel versions supported by the official Sentry Laravel SDK. Check the Sentry Laravel docs for the exact version matrix used by your application.

Can Telebugs track errors in queues and background jobs?

Yes. Events captured by the Sentry Laravel SDK from queues, jobs, workers, and background code can be sent to Telebugs with the surrounding context.

Can I customize Laravel error grouping?

Yes. Telebugs groups similar errors by default, and you can use custom grouping and fingerprinting rules when your Laravel app needs a different issue boundary.

Can Telebugs track API and webhook errors?

Yes. Laravel API routes, webhook handlers, controllers, middleware, and service classes can send captured exceptions to Telebugs through the Sentry Laravel SDK.

Can AI tools inspect Laravel errors through MCP?

Yes. Telebugs MCP support lets compatible AI tools inspect structured error context from Telebugs, including Laravel backtraces, breadcrumbs, queue metadata, release context, and event details, while keeping your server as the source of truth.

How do I handle sensitive data in Laravel errors?

Use the Sentry SDK scrubbing options and Telebugs server-side sensitive data scrubbing rules. Because Telebugs is self-hosted, you control where error data is stored and how long it is retained.

What developers are saying about Telebugs