Weave Code
Pail Laravel Package
laravel/pail
Laravel Pail tails your Laravel app’s logs in a sleek, interactive CLI. Works with any log driver (including Sentry and Flare) and includes handy filters to quickly find the messages you need while developing.
Dive into your Laravel application's log files directly from the console. 🪣
Frequently asked questions about Pail
- How do I install Laravel Pail for log tailing in my Laravel 12 app?
- Run `composer require --dev laravel/pail` in your project directory. No additional configuration is needed—just execute `php artisan pail` to start tailing logs interactively. The package integrates seamlessly with Laravel’s logging system without requiring migrations or service providers.
- Does Pail work with Sentry or Flare log drivers, or only file-based logs?
- Pail supports all Laravel log drivers, including Sentry, Flare, and custom Monolog handlers. It dynamically reads logs from your configured driver, so no extra setup is required for Sentry or Flare. Just install Pail and use the same CLI filters for any driver.
- Can I filter logs by severity level (e.g., only show errors) in Laravel Pail?
- Yes, Pail includes built-in filters for log levels. Use `--level=error` to show only errors, or `--level=debug,info` to combine levels. You can also filter by context (e.g., `--context=auth`) or time ranges for precise debugging.
- Will Pail slow down my Laravel application in production?
- No, Pail is designed for minimal overhead. Commands are lazy-loaded, and it only reads logs without modifying or writing to them. It’s safe for production debugging, especially with the `--timeout` option to limit runtime in CI/CD or ephemeral environments.
- How does Pail handle multiline logs or malformed JSON entries?
- Pail includes fixes for multiline logs (v1.2.3) and malformed JSON (v1.2.7). It gracefully parses edge cases while preserving the original log structure. If your logs contain custom formats, test with the `--raw` flag to ensure compatibility.
- Is Laravel Pail compatible with Laravel 13, or should I wait for updates?
- Pail is actively maintained for Laravel 11–13 and PHP 8.4–8.5. The latest version (v1.2.7) includes no deprecation warnings, and the package follows Laravel’s release cycle. Check the [Laravel docs](https://laravel.com/docs/logging#tailing-log-messages-using-pail) for version-specific notes.
- Can I use Pail in CI/CD pipelines (e.g., GitHub Actions) to debug failed tests?
- Yes, Pail is CI/CD-friendly. Use the `--timeout` flag to limit log tailing duration (e.g., `php artisan pail --timeout=30`) and avoid flaky tests. It’s ideal for inspecting logs in ephemeral environments where terminal access is available.
- What alternatives to Pail exist for Laravel log tailing, and why choose Pail?
- Alternatives include `tail -f storage/logs/laravel.log` (basic) or third-party tools like `laravel-debugbar` (for web UI). Pail stands out for its native Laravel integration, interactive filters, and support for all log drivers (Sentry, Flare, etc.) without external dependencies.
- How do I debug logs from a microservice architecture using Pail?
- Pail works independently for each service. Tail logs for a specific service by running `php artisan pail --context=service-name` or filtering by custom context keys. It’s useful for distributed debugging when combined with Laravel’s service container logging.
- Does Pail support real-time log streaming for high-traffic Laravel apps (e.g., 10K+ logs/sec)?
- Pail is optimized for performance with lazy-loaded commands, but for extreme log volumes, test responsiveness in your environment. If CLI lag occurs, consider using Pail for local debugging and web-based tools (Flare/Sentry) for production monitoring.
Weaver
How can I help you explore Laravel packages today?