Production monitoring often feels like a chore. You dig through logs after a crash. You wait for customer complaints to find slow endpoints. Laravel Pulse changes that workflow. It provides a real-time, at-a-glance dashboard for your application health.
Pulse is a first-party package. It lives directly inside your Laravel application. It tracks performance, usage, and errors without heavy infrastructure. Developers get immediate visibility into what matters most.
The Dashboard: Real-Time Health Check
Pulse delivers a bird's-eye view of your production environment. The dashboard uses a grid of "cards" to display data. These cards update in real-time as users interact with your site. You can see who is active and what they are doing.
The default layout covers the essentials. It shows application usage, slow routes, and server health. You can rearrange these cards to fit your screen. It is built with Livewire for a reactive experience.
Usage Tracking: Knowing Your Users
Pulse identifies your most active users. It tracks who makes the most requests and who dispatches the most jobs. This is not just for curiosity. It helps you find "noisy neighbors" who might be stressing your system.
The application usage card highlights three key metrics. It shows total requests, slow requests, and background jobs. You can see exactly which user account is hitting a specific bottleneck. Pulse resolves user names and avatars automatically using Gravatar.
Monitoring Bottlenecks: Speed and Stability
Performance issues rarely happen across the entire app. Usually, a few specific endpoints or queries cause the lag. Pulse makes these outliers visible immediately.
Slow Queries: Finding the Drag
Database queries are the most common source of slowness. Pulse records every query that exceeds a specific threshold. By default, this is 1,000ms. You can adjust this in your configuration file.
The slow queries card groups identical queries together. It shows you the raw SQL and the file location. You don't have to guess which Eloquent call is failing. You can jump straight to the code and optimize the index.
Slow Routes and Jobs
HTTP requests and background jobs also have dedicated cards. If a controller takes too long to respond, it appears here. If a queued job is struggling, you see it instantly. This helps you maintain a snappy user experience.
You can set per-route or per-job thresholds. Some tasks are naturally slower, like generating a large PDF. Pulse lets you define what "slow" means for different parts of your application. This prevents your dashboard from becoming cluttered with expected slow tasks.
Server Performance: Monitoring the Iron
Monitoring code is only half the battle. You also need to know how your hardware is holding up. Pulse includes a server recorder that tracks system resources.
System Metrics: CPU and RAM
The servers card displays CPU, memory, and disk usage. It works across multiple servers simultaneously. If you have a load balancer and three web nodes, Pulse shows all of them in one place.
You run a simple daemon command on each server to collect these stats. It uses the pulse:check Artisan command. This makes Pulse a viable alternative to complex external monitoring agents. It keeps your stack simple and unified.
Technical Implementation: Getting Started
Pulse is easy to install. It requires a MySQL, MariaDB, or PostgreSQL database for storage. Most Laravel developers already have one of these ready.
Installation and Setup
Start by requiring the package via Composer. You then publish the assets and run the migrations.
composer require laravel/pulse
php artisan vendor:publish --provider="Laravel\Pulse\PulseServiceProvider"
php artisan migrate
Once installed, you can access the dashboard at the /pulse route. By default, this route is only available in your local environment. You must authorize it for production use in your AppServiceProvider.
Configuration and Recorders
The config/pulse.php file controls everything. You can enable or disable specific recorders here. Recorders are the background workers that capture data.
Pulse includes recorders for:
- Cache interactions (hits and misses)
- Exceptions and errors
- Queues and job throughput
- Outgoing HTTP requests (using the Laravel HTTP client)
- Database queries
Performance at Scale
Monitoring tools can sometimes slow down the very app they are watching. Pulse is designed for low overhead. It uses several strategies to remain fast even under heavy traffic.
Redis Ingest and Sampling
For high-traffic sites, you can use the Redis ingest driver. Instead of writing directly to the database, Pulse pushes events to a Redis stream. A background worker then moves the data to permanent storage.
Sampling is another powerful feature. You can tell Pulse to only record 10% of requests. This provides a statistically accurate view without storing millions of rows. It keeps your database small and your dashboard fast.
Data Trimming
Pulse does not store data forever. It automatically trims old entries once they fall outside your dashboard window. This prevents your storage from growing indefinitely. You get the insights you need for the current day or week without the bloat.
Customization: Making Pulse Yours
Every application is unique. Sometimes the default cards aren't enough. Pulse is fully extensible because it is built on the TALL stack (Tailwind, Alpine.js, Laravel, Livewire).
Building Custom Cards
You can create your own Pulse cards using Livewire. For example, you might want a card that tracks sales in real-time. Or perhaps a card that monitors your API rate limits.
The process involves creating a Livewire component that extends Pulse's base Card class. You can then use the Pulse::record method to capture custom metrics. This data becomes available for display on your dashboard instantly.
Ecosystem Integration
Pulse fits perfectly with the rest of the Laravel ecosystem. If you use Laravel Forge or Laravel Cloud for deployment, Pulse provides the final layer of visibility. It works alongside Laravel Telescope for deep debugging and Laravel Horizon for queue management.
Telescope is for looking at every single event in detail. Pulse is for looking at the overall health of the system. Together, they provide a complete monitoring solution.
Future-Proof Monitoring
The Laravel team continues to refine Pulse. New features and cards are added regularly. It has become a standard part of the modern Laravel stack.
Pulse ensures you aren't flying blind. It turns performance data into actionable insights. You stop guessing where the bottlenecks are. You start shipping faster, more stable applications.
We invite you to install Pulse today. It only takes a few minutes to set up. Your production environment will thank you.