Weave Code
Pulse Laravel Package
laravel/pulse
Laravel Pulse is a real-time performance monitoring tool and dashboard for Laravel apps. Track key runtime metrics, identify slow requests and bottlenecks, and keep tabs on application health in production with minimal setup.
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 my Laravel 11+ application?
- Run `composer require laravel/pulse` and then execute `php artisan pulse:install`. This sets up the middleware, publishes config files, and creates the necessary database tables or Redis storage. Ensure your Laravel app is on PHP 8.2+ for compatibility.
- Does Laravel Pulse work with Laravel Forge or shared hosting environments?
- Yes, Pulse supports shared hosting as long as PHP 8.2+ and Redis (or database storage) are available. However, some features like real-time Livewire updates may require more robust server resources. Check your hosting provider’s PHP extensions and Redis support first.
- Can I monitor custom business events or metrics beyond default skills (e.g., HTTP, jobs, queries)?
- Yes, Pulse supports custom metrics via its 'skills' API. You can extend Pulse by creating custom skills to track events like business transactions, third-party API calls, or other application-specific metrics. The [official docs](https://laravel.com/docs/pulse#custom-skills) provide a guide for implementation.
- What’s the performance impact of using Laravel Pulse in production?
- Pulse is designed to be lightweight, with minimal overhead for default usage. It samples data to reduce storage and processing load, and you can adjust retention periods (e.g., `pulse.trim_duration`) to balance detail and performance. Benchmark in staging to confirm it meets your app’s needs.
- How does Laravel Pulse handle storage? Can I use a database instead of Redis?
- Pulse defaults to Redis for storage due to its speed and efficiency, but you can configure it to use a database (MySQL/PostgreSQL) by setting `PULSE_STORAGE=database` in your `.env`. Database storage may impact performance under high traffic and isn’t recommended for large-scale apps.
- Does Laravel Pulse support multi-server or distributed Laravel deployments?
- Yes, Pulse can monitor multiple servers by configuring a shared Redis instance or database. Ensure all servers point to the same storage backend. For high-traffic apps, consider tuning sampling rates or retention periods to avoid storage bottlenecks.
- Can I integrate Laravel Pulse with alerting systems like Slack or PagerDuty?
- Pulse doesn’t include built-in alerting, but you can trigger alerts by monitoring Pulse’s data (e.g., failed jobs, slow queries) via Laravel’s `scheduler` or third-party tools like Laravel Nova, Sentry, or custom scripts. Use Pulse’s API or database queries to fetch metrics for alerting logic.
- What Laravel versions does Pulse support, and is there backward compatibility?
- Pulse officially supports Laravel 10–13 and includes a `1.x` branch for older versions. If you’re on Laravel 9 or below, check the `1.x` branch or consider upgrading. Always test in staging before deploying to production.
- How do I exclude specific routes or middleware from Pulse monitoring?
- Use the `except` option in `config/pulse.php` to exclude routes or middleware. For example, add `'except' => ['admin.*', 'api/webhooks']` to skip monitoring sensitive or high-volume endpoints. This reduces noise and improves performance.
- Is Laravel Pulse a replacement for tools like Sentry or New Relic, or should I use it alongside them?
- Pulse is a lightweight, Laravel-native tool focused on request, job, and query monitoring—ideal for basic observability. For error tracking, session replay, or advanced APM features, pair it with Sentry, New Relic, or Datadog. Pulse excels at diagnosing performance bottlenecks within Laravel’s ecosystem.
Weaver
How can I help you explore Laravel packages today?