Log Viewer Laravel Package

Product Decisions This Supports

• Internal Developer Tools: Accelerate debugging by providing a self-service log viewer for engineers, reducing reliance on manual log file parsing or external tools like Sentry.
• Admin Panels: Embed a secure, production-ready log viewer in admin dashboards to monitor application health without exposing raw logs publicly.
• Observability Stack: Integrate with DevOps monitoring tools (e.g., Grafana, Datadog) by offering a filtered, downloadable log export for deeper analysis.
• Build vs. Buy: Replace custom log viewers (often fragile or outdated) with a maintained, feature-rich alternative that aligns with Laravel’s ecosystem.
• Compliance & Security: Enforce role-based access control (RBAC) for logs, ensuring sensitive data is only accessible to authorized personnel (e.g., DevOps, Security teams).
• Dark Mode & UX: Improve developer experience with dark themes, context expansion, and real-time filtering, reducing cognitive load during debugging.
• Log Retention & Archiving: Enable filtered log downloads for compliance audits or long-term storage, bridging gaps in Laravel’s native logging system.

When to Consider This Package

Adopt This Package If:

• Your Laravel app (v9–11) lacks a centralized log viewer and engineers manually grep storage/logs/.
• You need secure, role-restricted access to logs (e.g., for admins/DevOps) without exposing raw files.
• Your team debugs stack traces frequently and needs context-aware log expansion (e.g., ±5 lines around errors).
• You require real-time log tailing (e.g., for staging/production monitoring) with auto-refresh controls.
• Your admin panel or DevOps dashboard needs a production-ready, themed log viewer with minimal setup.
• You want to avoid reinventing the wheel—this package handles log rotation, path traversal protection, and middleware integration out of the box.
• Your team uses dark mode and needs consistent UI across tools.

Look Elsewhere If:

• You need log aggregation (e.g., ELK, Loki) or structured logging (e.g., JSON logs with fields like user_id). This package focuses on raw Laravel logs.
• Your logs are already centralized in a third-party tool (e.g., Datadog, New Relic), and this would be redundant.
• You require advanced query languages (e.g., SQL for logs) or alerting—this is a viewer, not a monitoring system.
• Your app uses non-Laravel logging (e.g., Monolog with custom handlers). While it detects laravel.log, it may not cover all edge cases.
• You need log retention policies or automated log cleanup—this package only exposes logs it finds.
• Your team prefers CLI tools (e.g., tail -f, stern) over web UIs. This is a browser-based solution.

How to Pitch It (Stakeholders)

For Executives:

"We’re proposing a secure, self-service log viewer for engineers and DevOps to debug issues faster without manual log parsing. This package:

• Reduces toil: Eliminates the need to SSH into servers or use external tools for log analysis.
• Improves security: Logs are never exposed publicly; access is restricted to authorized roles (e.g., admins, DevOps).
• Enhances observability: Real-time filtering, context expansion, and downloads enable proactive issue resolution.
• Low risk: MIT-licensed, Laravel-native, and production-tested with minimal setup. Cost: ~$0 (open-source). ROI: Faster debugging → fewer production incidents."

For Engineering/DevOps:

"This Laravel log viewer gives us:

• Dark mode + clean UI: No more squinting at light-on-dark logs.
• Context-aware debugging: Expand stack traces with ±5/±10 lines around errors.
• Real-time tailing: Watch logs live with auto-refresh (pause on scroll).
• Secure by default: Admin-only access, path traversal protection, and custom middleware.
• No reinvention: Handles log rotation, Laravel’s default log paths, and filtered downloads for audits. Just install, configure auth, and start debugging faster. Example:

composer require shaonmajumder/log-viewer
php artisan vendor:publish --tag=log-viewer-config

Then access /log-viewer (or your custom route)."

For Security Teams:

"This package mitigates log exposure risks by:

• Enforcing auth: Only logged-in users (or allowed emails) can access logs.
• Preventing path traversal: Hardened against malicious log path injection.
• Avoiding public exposure: Defaults to private routes (configurable).
• Compliance-ready: Filtered downloads for audits (e.g., GDPR, SOC2). No raw logs leak—just a controlled, monitored interface."