🔍 LogLens

Developer-focused application log analyzer and real-time monitoring dashboard for Laravel.
Lightweight • Zero Migrations • Zero Extra Database Queries • Production Hardened

🌟 What is LogLens?

LogLens is a modern, high-performance developer dashboard and diagnostic package built specifically for Laravel (versions 10, 11, 12, and 13). It brings together graphical log file management, HTTP latency metrics, database query observation, Apache server health, host OS and Docker container telemetry, background queue monitoring, and console scheduler observability into a single, cohesive interface.

Most monitoring tools pollute your application database with tens of thousands of telemetry rows or execute heavy diagnostic queries that slow down production clusters. LogLens operates under a strict Zero-Extra-Query & Zero-Migration architectural guarantee.

🛡️ Core Non-Negotiable Guarantees

[!IMPORTANT]

1. Strict Zero-Extra-Query Mode: LogLens never executes SQL queries on your application database solely for monitoring. Query profiling is 100% passive via Laravel's native DB::listen.
2. Zero Database Migrations: There are zero database tables to create, migrate, or maintain. All core operations run in bounded memory or an optional external adapter (e.g. Redis).
3. Zero Frontend Build Dependencies: Powered by pure Blade + Bootstrap 5 + Font Awesome 6 + Chart.js. No Tailwind CSS, Node, Vite, or npm build steps required.
4. Safe Native Probes Only: Never executes arbitrary shell commands from dashboard input. Missing OS metrics report null and are never fabricated as zero.
5. Safe by Default: Disabled out of the box (LOGLENS_ENABLED=false) with multi-tier authorization guards on all read and destructive endpoints.

🚀 Key Features

📋 Compatibility & Requirements

📦 Installation

Install LogLens via Composer:

LogLens supports Laravel package auto-discovery. The LogLensServiceProvider and LogLens facade will be registered automatically.

Publish Configuration

Publish the configuration file to config/loglens.php:

(Optional) Publish Blade views to customize the UI:

⚙️ Quick Start Configuration

By default, LogLens is disabled to ensure zero unintended overhead in production:

To enable the dashboard in your environment, add the following to your .env file:

Start your Laravel development server:

Navigate to: http://localhost:8000/loglens

🔒 Access Control & Authorization (Locking Down the Dashboard)

LogLens provides multiple defense-in-depth authorization layers to ensure that unauthorized users or the public cannot access your monitoring dashboard.

1. Custom Callback Authorization (Recommended)

In your app/Providers/AppServiceProvider.php, use the LogLens::auth() callback to restrict access strictly to authenticated team members:

[!NOTE] Any unauthenticated or unauthorized visitor attempting to access /loglens will immediately receive a 403 Forbidden response.

2. Standard Laravel Gate Integration

Alternatively, register standard Laravel Gates in your AuthServiceProvider (or AppServiceProvider in Laravel 11/12):

3. Automatically Redirect Unauthenticated Visitors to /login

If you want visitors without an active session to be automatically redirected to your application's login page instead of seeing a 403 page, simply add Laravel's native 'auth' middleware to config/loglens.php:

4. Restricting by IP Whitelist (Office / VPN Only)

To restrict dashboard access exclusively to specific static IP addresses or internal corporate VPNs:

5. Disable Local Environment Auto-Access

By default, LogLens allows direct access in local environments (APP_ENV=local) to make development convenient. To enforce strict authentication even on your local machine, set:

6. Obscure the Dashboard URL

You can change the URL prefix from /loglens to any secret path in your .env:

🗺️ Dashboard Directory & Routes

All routes are automatically prefixed under your configured LOGLENS_PATH (/loglens by default) and protected by the AuthorizeLogLens middleware:

🌐 Apache mod_status Live Monitoring

LogLens connects to Apache's native mod_status module to observe web server performance without exposing the status endpoint to the public.

Architecture

Setup Instructions

1. Enable mod_status in Apache:

2. Enable Apache monitoring in .env:

3. Run the background collector daemon:

⚡ Performance Benchmarks

Measured on PHP 8.3 using tests/Performance/PerformanceBenchmarkTest.php:

🧪 Testing & Quality Assurance

LogLens includes an exhaustive automated test suite covering unit, feature, security, and performance scenarios:

Strict Zero-Extra-Query Verification Test

🚀 Production Deployment Checklist

Before deploying LogLens to a live production cluster:

1. [ ] Master Switch Configured: Ensure LOGLENS_ENABLED=true in production .env.
2. [ ] Authorization Registered: Register LogLens::auth() in AppServiceProvider or define the viewLogLens Gate.
3. [ ] Destructive Actions Restricted: Keep LOGLENS_ALLOW_DESTRUCTIVE=false unless log truncation is explicitly authorized via LogLens::destructiveAuth().
4. [ ] Allowed Apache Hosts: If using Apache monitoring, verify LOGLENS_APACHE_STATUS_URL points to http://127.0.0.1/server-status?auto and allowed hosts are restricted.
5. [ ] Queue Backlog Strict Mode: Leave LOGLENS_QUEUE_POLL_BACKLOG=false to ensure zero database queries on queue monitoring dashboards.
6. [ ] Redis Prefix Isolation: If multiple applications share a Redis instance, configure distinct LOGLENS_REDIS_PREFIX=myapp:loglens:metrics.
7. [ ] Alert Thresholds: Adjust CPU, Memory, Disk, and HTTP error rate alert thresholds in config/loglens.php to match your infrastructure capacity.

🤝 Contributing

Contributions, bug reports, and pull requests are welcome! Please review CONTRIBUTING.md for details on code style, testing, and submission guidelines.

🔒 Security Policy

If you discover a security vulnerability within LogLens, please review our Security Policy.

📄 License

LogLens is open-sourced software licensed under the MIT license.

Crafted with care by Mehrab Hossain • Made for Laravel Developers