Introduction

quiet-guard/laravel-monitor is the official Laravel client SDK for Quiet Guard. You install it with Composer in the application you want to monitor; its service provider and the Monitor facade are auto-discovered, so there is no manual registration to do.

Once configured with three environment variables (MONITOR_ENABLED, MONITOR_URL, MONITOR_KEY), the SDK registers an additive callback on Laravel's exception handler: every reported exception is forwarded to your dashboard without touching your own logging. Capture is fail-safe, a network or configuration error inside Quiet Guard is swallowed and never affects the monitored app.

What it does

• Exception reporting: automatic capture through the framework's exception handler, plus a manual Monitor::report() API. See Exception reporting.
• Application logs: opt-in forwarding of MessageLogged events, buffered and sent in a single batch per request. See Logging.
• Dependency scanning: the monitor:dependencies command ships your composer.lock so the server can flag known vulnerabilities. See Dependency scanning.
• Heartbeats: the monitor:heartbeat command and the ->monitorHeartbeat() scheduler macro ping the server from your scheduled tasks so it can alert you when they go silent. See Heartbeats.
• Encrypted backups: the monitor:backup / monitor:restore commands store database dumps or folders in the zero-knowledge vault, encrypted client-side. See Encrypted backups.
• Privacy by default: sensitive keys (passwords, tokens, cookies, authorization headers) are scrubbed before anything leaves your server.

Built on the PHP core

The SDK is a thin Laravel adapter over quiet-guard/monitor-php, the framework-agnostic core. The two share the same ingestion contract and the same backup cipher, so the Laravel, Symfony and WordPress clients all speak the platform-neutral ingestion API documented in the server docs.

Requirements

• PHP 8.2 or higher
• Laravel 11, 12 or 13
• A Quiet Guard server and a per-project API key

The next pages walk through installation, configuration and day-to-day usage.