Laravel Pulse

Laravel Pulse is a real-time application performance monitoring tool and dashboard for Laravel applications. It surfaces at-a-glance insights into the health of your app, spotlighting slow database queries, jobs, and requests, exception hotspots, cache usage, and the users and routes generating the most load.

Pulse captures metrics through lightweight, sampling-friendly recorders and displays them on a customizable Livewire dashboard you can extend with your own cards. Because it stores its data in your own database and runs inside your application, you get production observability without shipping data to a third-party service.

What You Get

• A real-time Livewire dashboard summarizing application performance
• Built-in recorders for slow queries, requests, jobs, exceptions, and cache usage
• Server resource cards showing CPU, memory, and storage over time
• Usage tracking for the busiest users, routes, and jobs
• An extensible card and recorder API for custom metrics

Common Use Cases

• Spotting slow database queries and N+1 hotspots in production
• Monitoring queue throughput and identifying slow or failing jobs
• Tracking exception frequency and the routes that trigger them
• Understanding which users and endpoints drive the most load

Under The Hood

Architecture - Pulse boots via src/PulseServiceProvider.php and centers on the Pulse.php coordinator, which buffers Entry and Value records captured by classes in src/Recorders (SlowQueries, SlowRequests, SlowJobs, Exceptions, CacheInteractions, Servers, and usage recorders). Captured data flows through src/Ingests into src/Storage, and the dashboard is composed of Livewire components in src/Livewire that read aggregated values.

Tech Stack - PHP with Blade and a Livewire-based front end (roughly 80% PHP, 20% Blade). It integrates deeply with Laravel’s event, queue, cache, and database layers and persists metrics to a configurable storage driver in the host application’s database.

Code Quality - The repository uses Pest with Feature and Unit suites, fixtures, and a StorageFake for deterministic tests. Code is organized into clear concerns (Recorders, Ingests, Storage, Livewire, Support) and is actively maintained by the Laravel team with frequent releases.

API Design - Adoption is largely configuration-driven: enable recorders and sampling rates in config, publish the dashboard, and optionally register custom cards. The Pulse facade plus a small Recorder/Card contract set make extending the dashboard approachable for teams that need bespoke metrics.