Laravel Log Viewer Laravel Package

Product Decisions This Supports

• Debugging & Observability Roadmap: Accelerates development cycles by providing a lightweight, built-in log viewer for Laravel applications, reducing reliance on external tools like Sentry or Datadog for basic log inspection.
• Build vs. Buy: Avoids reinventing the wheel for a log viewer, saving engineering time and reducing technical debt. The MIT license ensures no licensing costs.
• DevOps & SRE Use Cases: Enables faster incident response by giving engineers a quick, self-service way to inspect logs without requiring CLI access or log aggregation tools.
• Security & Compliance: Simplifies log auditing for compliance checks (e.g., GDPR, SOC 2) by centralizing log access in a controlled UI.
• Multi-Environment Support: Works seamlessly across Laravel/Lumen apps in staging, production, and local environments, reducing friction for cross-team debugging.

When to Consider This Package

• Look Elsewhere If:

  • You need advanced log analytics (e.g., query syntax, filtering, or retention policies) → Consider Laravel Horizon or ELK Stack.
  • Your logs are sensitive/regulated (e.g., PII, PCI) → Use role-based access control (RBAC) or integrate with a SIEM tool (e.g., Splunk).
  • You require log shipping to external systems (e.g., AWS CloudWatch, Datadog) → Use Laravel’s built-in log channels or Fluentd.
  • Your team prefers CLI-based tools (e.g., tail, grep) → Stick with native Laravel logging or Laravel Telescope.
  • You’re using Laravel 5.x or below → This package supports Laravel 6+ only.
  • You need real-time log streaming → Consider WebSocket-based solutions (e.g., Laravel Echo + Pusher).

• Adopt If:

  • You need a quick, zero-config log viewer for Laravel/Lumen.
  • Your team lacks dedicated DevOps resources to manage log aggregation tools.
  • You’re in early-stage development and want to avoid over-engineering observability.
  • You prioritize simplicity over scalability for log inspection.

How to Pitch It (Stakeholders)

For Executives:

*"This package lets our engineering team inspect Laravel application logs in real-time through a simple web interface—no third-party tools or setup required. It’s like ‘tail -f’ but in a browser, which will:

• Reduce debugging time by 30%+ (anecdotal, based on similar tools).
• Lower costs by eliminating the need for log aggregation tools in early-stage projects.
• Improve collaboration by giving non-engineers (e.g., support, QA) visibility into errors without CLI access. We’re proposing a lightweight, MIT-licensed solution that integrates in 10 minutes—ideal for our Laravel stack. The trade-off is minimal: it’s not for long-term log retention or advanced analytics, but it covers 80% of our debugging needs today."*

For Engineering:

*"This is a drop-in log viewer for Laravel/Lumen that:

• Works out of the box with zero public assets or vendor route conflicts.
• Supports Laravel 6–12 and Lumen, so it’s future-proof for our stack.
• Integrates seamlessly with existing logging (single/multi-file, rotated or not).
• Saves time by replacing tail -f storage/logs/laravel.log with a searchable UI.

Proposal:

1. Add via Composer (composer require rap2hpoutre/laravel-log-viewer).
2. Register the service provider and route (5-minute setup).
3. Restrict access to APP_ENV=local or behind a firewall for security.

Alternatives considered:

• Laravel Telescope: Overkill for pure log viewing (focuses on requests, commands, queues).
• Sentry/Datadog: Expensive and complex for basic log inspection. This fills the gap for quick, self-service log access without bloat."*

Note: The original package URL in the README points to mannysoft/laravel-log-viewer, but the description and screenshots reference rap2hpoutre/laravel-log-viewer. Assuming the latter is the correct/active package.