- How do I install and set up kahovskaia/laravel-log-viewer in my Laravel project?
- Run `composer require kahovskaia/laravel-log-viewer` to install. The package integrates seamlessly with Laravel’s native logging system (Monolog) and requires no additional configuration for basic usage. If you need a UI, pair it with a frontend solution like Livewire or Inertia.js to display logs in a Blade view or component.
- Does this package support Laravel 10? What about older versions like Laravel 8 or 9?
- The package likely supports Laravel 8.x and 9.x based on typical adoption patterns, but check the `composer.json` for explicit version constraints. For Laravel 10, you may need to use the `dev-main` branch or fork the package to ensure compatibility, as it appears unmaintained with low community activity.
- Can I filter or search logs using this package? For example, show only errors or warnings from the last hour.
- Out of the box, this package provides basic log reading without built-in filtering or search. You’ll need to extend it manually—either by parsing logs in your application code or integrating a frontend solution (like Livewire) to add custom filters for log levels, dates, or keywords.
- Will this package work with custom log paths or non-standard log formats (e.g., JSON logs)?
- The package reads Laravel’s default log files (e.g., `storage/logs/laravel.log`) by default. For custom paths, you’ll need to configure the log reader to point to your specific file. JSON logs or structured formats aren’t natively supported; you’d need to pre-process logs or write a custom parser to handle them.
- Is there a way to view logs in real-time, like tailing a log file, without refreshing the page?
- No, this package doesn’t support real-time log streaming. It reads logs as static files, so updates require manual refreshes or a frontend solution (e.g., Livewire with polling) to simulate real-time behavior. For true real-time logs, consider alternatives like Laravel Horizon or third-party tools.
- How does this package handle large log files? Will it impact my application’s performance?
- The package reads logs sequentially, which could slow down your app if log files are very large (e.g., multi-GB). For better performance, implement chunked reading or pagination in your UI layer. Test with your expected log size to ensure responsiveness, especially in production-like environments.
- Does kahovskaia/laravel-log-viewer support log rotation or multiple log files (e.g., daily logs)?
- The package reads the primary Laravel log file by default. For rotated logs (e.g., `laravel-2023-10-01.log`), you’ll need to manually configure it to scan and merge files or extend the package to handle log rotation. There’s no built-in support for multi-file setups.
- Are there security concerns with exposing logs in the browser? For example, will sensitive data (API keys, passwords) be visible?
- The package doesn’t sanitize logs by default, so sensitive data like tokens or passwords may appear in plaintext. If your logs contain PII, use Laravel’s log filtering (e.g., Monolog processors) or mask data before displaying logs. Avoid using this in production without proper safeguards.
- What are some alternatives to kahovskaia/laravel-log-viewer for Laravel log inspection?
- For a more feature-rich solution, consider **Laravel Horizon** (real-time logs and jobs), **Laravel Ray** (advanced debugging with log inspection), or **Spatie’s Laravel Log Viewer** (if available). For CLI-based tools, `tail -f storage/logs/laravel.log` or **Laravel Telescope** (if you need deeper debugging) are solid alternatives.
- How can I integrate this package with a frontend framework like Livewire or Inertia.js to display logs?
- Use the package’s log-reading functionality to fetch entries (e.g., via a service or facade) and pass them to a Livewire component or Inertia.js page. For example, create a Livewire component that queries the logs and renders them in a table with pagination or search. The package itself doesn’t include a UI, so you’ll need to build that layer.