leventcz/laravel-top
Laravel Top is a lightweight CLI dashboard for real-time monitoring of Laravel apps in production. It listens to request events and aggregates short-lived metrics in Redis to show throughput, latency, errors, and busiest routes across all servers.
Architecture fit: Seamlessly integrates with Laravel's event system and Redis for real-time HTTP request monitoring. Leverages existing infrastructure without external dependencies but ignores queue/command metrics. Short-TTL Redis storage prevents data bloat but inherently limits historical analysis. Best suited for transient production diagnostics rather than long-term trend tracking.
Integration feasibility: Simple Composer installation with minimal config publishing. Requires Redis 5.0+ (already standard in Laravel stacks) but has unclear behavior for recording_mode=always when application isn't running. No database migrations or complex setup needed.
Technical risk: Low adoption (0 dependents) raises maintenance concerns. Potential Redis write bottlenecks under high traffic (>10k RPS) despite aggregation. Critical gap: no documented error handling for Redis failures, risking application crashes during outages. The 2025 release date in metadata appears erroneous, indicating versioning issues or potential repository instability.
Key questions: How does Redis write volume scale at >5k RPS? What specific failure modes occur during Redis downtime? Does recording_mode=always actually function outside HTTP contexts? Are there known memory leaks in the event listener?
Stack fit: Ideal for Laravel 10-12 and Octane environments with existing Redis. Requires PHP 8.2+ and predis/predis or phpredis extension. No external services needed beyond standard Laravel stack components.
Migration path: Minimal friction – composer require followed by optional php artisan vendor:publish --tag="top". Zero database migrations required. Configuration defaults work out-of-the-box for most setups.
Compatibility: Confirmed compatible with Laravel 10-12 (per v1.2.0 release) and Octane. Only supports HTTP request metrics (queues/commands excluded). Redis connection must match Laravel's primary DB config.
Sequencing: Install → configure Redis connection (if non-default) → run php artisan top immediately. For facade usage, wrap in custom CLI commands or admin UIs. Always verify Redis availability before production deployment.
Maintenance: High risk due to low adoption (0 dependents) and minimal community activity. No commercial support options. Requires proactive monitoring of GitHub issues for fixes. Mitigate by forking if critical issues arise.
Support: Relies solely on open-source GitHub issues. No SLAs or dedicated support channels. Teams must self-serve or build internal expertise.
Scaling: Handles moderate traffic well due to 5-second aggregation window and TTL cleanup. High-traffic environments (>10k RPS) risk Redis write contention – monitor redis_memory_used and redis_commands_processed. Multi-server setups require shared Redis instance (not separate containers).
Failure modes: Redis downtime causes immediate metric loss and potential application crashes (no fallback handling). Stale metrics during idle periods (appears as 0 values). Misconfigured Redis connections lead to silent failures.
Ramp-up: Near-zero learning curve for Laravel developers. php artisan top works immediately post-installation. Facade usage follows standard Laravel patterns. Teams can start using within 5 minutes of installation. Documentation is sufficient for basic use but lacks advanced troubleshooting guidance.
How can I help you explore Laravel packages today?