Weave Code
Pulse Laravel Package
laravel/pulse
Laravel Pulse is a real-time performance monitoring tool and dashboard for Laravel. Track requests, slow queries, jobs, cache usage, and other application metrics to spot issues quickly and keep your app healthy in production.
Laravel Pulse is a real-time application performance monitoring tool and dashboard for Laravel apps. It helps you observe key runtime metrics and behavior as they happen, making it easier to spot regressions, bottlenecks, and unusual activity during development and in production.
Built for the Laravel ecosystem, Pulse provides an integrated, first-party experience with clear visuals and actionable insight.
- Real-time dashboard for app health and performance signals
- Track request / response behavior and runtime trends
- Monitor slow operations to identify bottlenecks
- Designed for Laravel-first integration and workflows
- Open source, MIT licensed
Frequently asked questions about Pulse
- What Laravel versions does Pulse officially support, and should I use it with Laravel 10 or 11?
- Pulse officially supports Laravel 10+, but Laravel 13+ is recommended for full compatibility with the latest features. If you're on Laravel 10, ensure you’re using PHP 8.1+ and check the [official docs](https://laravel.com/docs/pulse) for version-specific notes. Pulse is designed to work seamlessly with Laravel’s latest updates, so upgrading is encouraged for stability.
- How do I install Laravel Pulse in an existing Laravel project?
- Install Pulse via Composer with `composer require laravel/pulse`, then publish its assets and config using `php artisan pulse:install`. Run the migrations with `php artisan migrate`, and start the queue worker (`php artisan queue:work`) to process metrics. The dashboard is accessible at `/pulse` once Livewire is installed (included by default in Laravel 10+).
- Does Pulse work with Laravel Forge or Valet for local development?
- Yes, Pulse works with Forge, Valet, and other Laravel hosting solutions. Ensure your environment has Redis or a database configured for storage, and the `pulse:work` queue worker is running. For local testing, use `php artisan serve` alongside the queue worker. Pulse’s Livewire dashboard will function as long as your Laravel app is accessible via a browser.
- Can I monitor custom metrics or third-party services (e.g., Stripe, Algolia) with Pulse?
- Pulse supports custom metrics via custom cards. You can create your own cards to track business KPIs or integrate third-party services by extending the `Card` class. Check the [documentation](https://laravel.com/docs/pulse#custom-cards) for examples. For Stripe or Algolia, validate compatibility with Pulse’s event system or use Laravel’s logging to feed data into Pulse manually.
- Will Pulse slow down my Laravel application in production? How does it impact performance?
- Pulse is designed for low overhead, using Laravel’s built-in event listeners and middleware to collect metrics without significant performance impact. However, high queue volumes may introduce latency if the `pulse:work` queue isn’t optimized. Use `PULSE_SAMPLE_RATE` to sample metrics if needed, and monitor the queue worker’s performance separately. Benchmark in staging before full deployment.
- How does Pulse handle data retention, and can I reduce storage usage?
- Pulse retains data for 14 days by default, configurable via `PULSE_RETENTION_DAYS`. To reduce storage, lower this value or prune old data manually. For Redis storage, ensure your cache driver is configured properly. If storage bloat is a concern, consider using a separate database for Pulse or implementing a custom cleanup script.
- Can I use Pulse alongside Laravel Telescope? Will they conflict?
- Pulse and Telescope can coexist, but they serve different purposes—Telescope focuses on debugging (logs, requests, exceptions), while Pulse is for real-time operational metrics. Disable Telescope’s queue listeners if both are active to avoid duplicate processing. Pulse is lighter for production monitoring, while Telescope is better suited for development debugging.
- What happens if the `pulse:work` queue worker crashes or stops running?
- If the `pulse:work` queue worker fails, Pulse will stop processing metrics, and the dashboard will show stale or incomplete data. Monitor the worker’s health using Laravel’s queue monitoring tools. Restart the worker with `php artisan queue:work` or use a process manager like Supervisor to ensure uptime. Critical metrics like HTTP requests may still log via middleware, but real-time updates will halt.
- Does Pulse support monitoring Laravel Livewire components and their performance?
- Yes, Pulse monitors Livewire component interactions, including load times and errors. It tracks Livewire hooks (e.g., `mount`, `hydrate`) and logs exceptions. This is useful for identifying slow or failing Livewire components in real time. Ensure Livewire is installed (v3+ recommended) and the `pulse:work` queue is running to capture these metrics accurately.
- Are there alternatives to Pulse for Laravel monitoring, and when should I consider them?
- Alternatives include New Relic, Datadog, or Laravel-specific tools like Laravel Debugbar (for debugging) or Sentry (for error tracking). Use Pulse if you need a lightweight, real-time dashboard for operational metrics without external dependencies. Choose third-party tools like New Relic if you require advanced APM features (e.g., distributed tracing, deep performance analysis) or enterprise support.
Weaver
How can I help you explore Laravel packages today?