A comprehensive log viewer package for Laravel applications with API support, filtering, and multi-language UI.
LogViewer is a Laravel package that provides a graphical interface and API for viewing, filtering, and managing application log files. It solves the problem of manually digging through text-based logs by offering a structured dashboard with search, pagination, and deletion capabilities.
Laravel developers and teams who need to monitor and debug their applications through log files, especially those working on projects with extensive logging requirements.
Developers choose LogViewer because it's a mature, feature-rich solution specifically built for Laravel with out-of-the-box functionality, excellent localization support, and the flexibility to work as both a UI and API.
:page_with_curl: Provides a log viewer for Laravel
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Includes pre-built views, routes, and controllers with no asset publishing required, making setup quick and eliminating custom development for basic log viewing.
Supports over 30 localizations, including Arabic, Spanish, and Japanese, which is ideal for international teams and projects with diverse user bases.
Can be used as a standalone API, allowing developers to integrate log data into other systems or build custom frontends without relying on the UI.
Optimized for big log files with grouped logs by dates and levels, ensuring performance doesn't degrade with extensive logging, as noted in the README.
Claims 100% code coverage and comprehensive documentation, aiding in reliability and reducing debugging time for developers.
Only compatible with Laravel 5.x to 11.x, making it unusable for projects on other PHP frameworks or vanilla PHP, which limits its versatility.
Focuses on static log file management without live streaming or real-time updates, which can be a drawback for dynamic monitoring and instant error detection.
While it supports custom storage paths, integrating non-standard log formats or external systems may require additional configuration and development effort.
The full dashboard and API might introduce unnecessary complexity for projects with minimal logging needs, where simpler tools could suffice.