Weave Code
Pulse Laravel Package
laravel/pulse
Laravel Pulse is a real-time application performance monitoring tool and dashboard for Laravel apps, surfacing slow requests, usage, and server health so you can spot bottlenecks fast.
Laravel Pulse is a real-time application performance monitoring tool and dashboard for your Laravel application.
Frequently asked questions about Pulse
- How do I install Laravel Pulse in a Laravel application?
- Install Laravel Pulse with composer require laravel/pulse, then publish its configuration using the Pulse service provider and run php artisan migrate. Configure environment values such as PULSE_TRIM_DURATION and PULSE_REDIS_CONNECTION, and make sure the queue worker used for Pulse ingestion is running.
- Which Laravel versions are supported by Laravel Pulse?
- Pulse is tightly coupled to Laravel releases; for example, Pulse v1.7.x requires Laravel 11 through 13. Check the Composer constraints for your chosen Pulse version before upgrading Laravel, since a Laravel upgrade may require a matching Pulse update. The package's supported range includes 1.0.x through 1.7.x, but exact compatibility depends on the version.
- Does Laravel Pulse require Redis?
- Pulse relies on Redis for real-time data processing and for caching and queueing, so Redis downtime or misconfiguration can disrupt monitoring. Set PULSE_REDIS_CONNECTION to the Redis connection Pulse should use and ensure that connection is highly available. Metrics are retained in your database, so also plan database storage and retention.
- How do I secure the /pulse dashboard endpoint?
- Pulse exposes a /pulse dashboard endpoint, so you must restrict access with middleware such as auth:sanctum or a custom authorization callback. Review the dashboard route configuration before production and consider IP restrictions or rate limiting for sensitive environments. Also confirm how sensitive metrics are sanitized before storage.
- How long does Laravel Pulse retain monitoring data?
- Retention is controlled by trim_duration, with examples such as 7d or 30d. Choose a window that balances troubleshooting needs with database storage costs. Large applications should plan to archive or optimize old Pulse data as volume grows.
- What performance overhead does Laravel Pulse add?
- Pulse is lightweight and Laravel-native, avoiding a standalone APM agent, but it still samples and records requests, queues, cache events, and exceptions. Benchmark under your workload and test the pulse:work queue backlog at peak load. You can disable pulse:check when isolating baseline overhead.
- Can I track custom metrics or business KPIs with Laravel Pulse?
- Yes. Pulse can record application-specific metrics through Pulse::record(), and its modular skills/plugins can extend monitoring for queues, databases, Livewire, and other areas. Check for existing skills for third-party packages before building custom ones.
- Do I need to run a queue worker for Laravel Pulse?
- Pulse uses Laravel's queue system for real-time data ingestion, and the documentation references a pulse:work worker. Ensure queue workers are running and monitor the pulse:work backlog under peak load so monitoring data stays current. Custom queue workers should be reviewed for compatibility with Pulse's sampling logic.
- Does Laravel Pulse work with Livewire and Laravel Horizon?
- Pulse has native integration with Laravel Livewire and queue systems such as Horizon, giving full-stack visibility. Potential edge cases can appear with newer Livewire versions or custom queue workers, so test those combinations. Keep Pulse and Laravel updated together to pick up compatibility fixes.
- Is Laravel Pulse a good alternative to New Relic or Datadog?
- Pulse is a lightweight, Laravel-native monitoring dashboard rather than a full standalone APM platform like New Relic or Datadog. It reduces architectural friction for Laravel apps and covers slow requests, queues, cache hits, and exceptions, but it is not designed for polyglot or infrastructure-wide monitoring. Audit overlap with existing Sentry, Blackfire, or APM tools before adopting it.
Weaver
How can I help you explore Laravel packages today?