Filament Log Viewer Laravel Package

Product Decisions This Supports

• Observability & Debugging Roadmap: Accelerates the development of a self-service log inspection tool for developers, reducing reliance on external tools (e.g., Laravel Horizon, third-party log aggregators) and improving time-to-resolution for production issues.
• Build vs. Buy: Buy—avoids reinventing a UI for log management while leveraging Filament’s admin panel ecosystem. Justifies investment if the team already uses Filament for other admin tasks.
• Use Cases:
  • DevOps/Engineering Efficiency: Replace manual tail -f storage/logs/laravel.log with a searchable, filterable UI.
  • Incident Response: Quickly triage errors by filtering by log level (error, warning), timestamps, or keywords (e.g., Auth, Payment).
  • Compliance/Audit: Retain log visibility without exposing raw files to non-technical stakeholders (access control via Filament’s built-in RBAC).
  • Onboarding: Reduce context-switching for new hires by centralizing logs alongside other admin panels (e.g., users, settings).

When to Consider This Package

• Adopt if:

  • Your team uses Filament for admin panels and needs a native log viewer without integrating third-party tools.
  • Logs are critical for debugging but currently require CLI access or external tools (e.g., Sentry, Datadog).
  • You prioritize speed of implementation (install in <30 mins) over custom features (e.g., log archiving, alerts).
  • Your Laravel logs are stored locally (not shipped to a SIEM or cloud provider).

• Look elsewhere if:

  • You need log aggregation (e.g., multi-server logs, historical analysis)—consider Laravel Horizon or Papertrail.
  • Your logs are structured/JSON-based and require advanced querying (e.g., ELK Stack, Loki).
  • You require real-time streaming or alerting (e.g., error thresholds).
  • Your team prefers tailored UIs (e.g., custom dashboards) over Filament’s default styling.
  • You’re using Laravel 10+ but the package lacks compatibility (check the version table).

How to Pitch It (Stakeholders)

For Executives:

"This package lets our engineering team search and filter Laravel logs directly from our existing admin panel—no more digging through CLI or third-party tools. It’s a low-code solution that cuts debugging time by 30%+ for common issues (e.g., auth failures, payment errors). Since it integrates with Filament, we avoid vendor lock-in and keep costs down. Ideal for teams already using Filament; minimal dev effort for high ROI."

For Engineering:

*"Pros:

• Instant setup: Drop-in Filament plugin with zero backend changes.
• Rich filtering: Search by log level, date, or keyword (e.g., Queue, Database).
• Stack traces: Click to expand errors—no more copying/pasting log snippets.
• RBAC: Leverage Filament’s permissions to restrict access (e.g., only DevOps sees logs).

Cons:

• No log retention/archiving (logs still follow Laravel’s default storage).
• Limited to single-server logs (no distributed tracing).

Ask: Can we trial this for our next incident? If it saves 2 hours/week on debugging, it pays for itself in a month."*

For Developers:

*"Why this over Horizon/Sentry?

• No extra services: No need to configure Horizon queues or Sentry DSNs.
• Consistent UI: Logs live alongside other Filament panels (e.g., users, settings).
• Lightweight: ~500 LOC vs. Horizon’s complexity.

Trade-offs:

• No log shipping (e.g., to Datadog)—use this for local/dev logs, not production-scale observability.
• Custom log formats may need minor tweaks (e.g., monolog context data).

Next steps:

1. Install via Composer: composer require achyutn/filament-log-viewer.
2. Publish the config: php artisan vendor:publish --provider="Achyutn\FilamentLogViewer\FilamentLogViewerServiceProvider".
3. Add to Filament’s navigation: resources/views/filament/navigation.blade.php."*