zanbug / laravel

v2.0.4 2026-10-15 09:24 UTC

Requires

• php: >=7.0
• illuminate/support: >=5.5
• zanbug/php-sdk: ^2.0.0

MIT

• Zanbug

• monitoring
• laravel
• error-monitoring
• error-tracking
• zanbug

Published on Packagist.org on 2026-10-15 09:24 UTC

README

Zanbug SDK — Laravel

Automatic exception, request, auth-user & session capture for Laravel (5.5 → 12), on top of the framework-agnostic zanbug/php-sdk core.

Install

composer require zanbug/laravel

The service provider is auto-discovered. Optionally publish the config:

php artisan vendor:publish --tag=zanbug-config

Configure — .env

ZANBUG_API_KEY=bb_xxxxxxxx
ZANBUG_HOST=https://zanbug.com
ZANBUG_CAPTURE_REQUESTS=true      # optional: per-request performance logs
ZANBUG_CAPTURE_QUERIES=true       # optional: slow-query monitoring (default: on)
ZANBUG_SLOW_QUERY_MS=1000         # optional: report queries slower than this (ms)
ZANBUG_CAPTURE_LOGS=true          # optional: forward Log::error()+ to Zanbug (default: off)
ZANBUG_LOG_LEVEL=error            # optional: minimum PSR level forwarded (default: error)

That's it. Every exception Laravel reports is sent to Zanbug together with the authenticated user, session id and request. No code changes required.

Manual capture

try {
    // ...
} catch (\Throwable $e) {
    \Zanbug\Sdk\Zanbug::capture($e, ['order_id' => 123]);
}

Log capture

With ZANBUG_CAPTURE_LOGS=true, a Monolog handler is pushed onto the default log channel and forwards every record at/above ZANBUG_LOG_LEVEL (default error) to Zanbug — so Log::error('...'), Log::critical('...') and caught-and-logged errors that never re-throw are no longer missed. File logging is unaffected (the handler bubbles). Records that carry a Throwable in their context are skipped, because Laravel's reported exceptions are already captured — this avoids reporting the same uncaught exception twice.

Background runs (Artisan, scheduler, queue)

Nothing to configure. Every Artisan command, scheduled task and queue job becomes a run in the panel's Processes tab (duration, CPU, memory, query count, slow queries, exit code, error). The provider listens to CommandStarting, ScheduledTaskStarting and JobProcessing, so a queue:work worker is split into its jobs and a schedule:run into its tasks. Slow queries captured inside a job are attributed to that job. Turn it off with ZANBUG_CAPTURE_RUNS=false.

Updating the SDK

php artisan zanbug:update --check     # exit 10 when a newer version is published
php artisan zanbug:update             # composer require zanbug/php-sdk:^<latest> zanbug/laravel:^<latest>
php artisan zanbug:update --dry-run

Automatic: ZANBUG_AUTO_UPDATE=true schedules zanbug:update --yes daily (needs your schedule:run cron; withoutOverlapping, runs in background). Restart queue:work / Horizon afterwards so workers load the new code.

How it works

• Hooks Laravel's MessageLogged event and forwards any logged exception (level error+).
• Resolves rich context (auth user, session, request) lazily via the core context_resolver.
• When ZANBUG_CAPTURE_REQUESTS=true, pushes request timing to /api/ingest/requests via a terminable middleware added to the web and api groups.
• Slow queries: listens to DB::listen on every connection (MySQL/PostgreSQL/SQLite/...); queries slower than ZANBUG_SLOW_QUERY_MS (default 1000 ms) are batched and sent non-blocking at shutdown to /api/ingest/queries, with the app caller file/line, connection name and redacted bindings.

PHP 7.1 → 8.4 compatible.