Download the PHP package amjdhsan/larascope without Composer

LaraScope

A Laravel package that logs HTTP requests, duration, status, SQL queries, and memory usage — with a built-in web dashboard to browse and inspect them.

Features

• Zero-config setup — auto-discovered and auto-registered into the web and api middleware groups
• Request metadata — method, URL, path, named route, IP address, authenticated user ID, status code
• Performance data — request duration (ms) and peak memory usage (MB)
• SQL query logging — captures all queries with bindings and execution time; automatically flags slow queries
• Sensitive header redaction — strips Authorization, Cookie, and X-CSRF-Token headers before persisting
• Privacy-first — request and response bodies are off by default
• Built-in dashboard — paginated log browser at /larascope with advanced filters, sorting, a summary strip and dark mode
• Log pruning — php artisan larascope:prune removes logs older than a configurable retention period
• Database fallback — if a DB insert fails, the payload is written to the Laravel log so nothing is silently lost
• Octane-safe — per-request state is reset on every handle() call to prevent bleed between requests

Requirements

Installation

Install the package via Composer:

The package is auto-discovered — no manual provider registration needed.

Coming from amjad-ah/larascope? That package is abandoned as of 2.0.0. The package name, the root namespace (AmjadAH\LaraScope\ → Amjad\LaraScope\) and the table schema all changed — see CHANGELOG.md for the upgrade steps.

Run the migration to create the larascope_request_logs table:

That's it. LaraScope is now logging every HTTP request in the web and api middleware groups.

Dashboard

Open /larascope in your browser to browse captured logs.

The list view opens with a summary strip — request count, error rate, average and slowest duration, and how many requests ran a slow query — computed over whatever the active filters match, so the figures always describe the rows below them.

Each row draws its duration as a bar scaled against the slowest request on the page, so an outlier is visible before you read a number. The bar turns amber when the request ran a slow query.

The detail view shows the full SQL query log (with bindings, per-query timing bars and slow-query flags), request headers, memory peak, and duration.

Filters

Filters combine with AND, and every one is a plain query-string parameter — bookmark a filtered view or share the URL.

Unknown, blank and malformed values are ignored rather than raising an error, so a hand-edited URL can never break the page. Active filters appear as chips above the table; each chip's × removes just that one filter.

Tailwind CSS is loaded via CDN — no asset pipeline required. The dashboard follows your OS light/dark preference and remembers the toggle in localStorage.

Protecting the dashboard in production

Add Laravel's auth middleware (or any middleware you prefer) to the dashboard:

Configuration

Publish the config file to customise any option:

Environment variables

Full config reference

Excluding paths and methods

Skip specific routes using wildcards (powered by Str::is()):

The dashboard's own routes are always excluded automatically to prevent recursive log growth.

Captured data

Each log entry stores 16 fields:

Indexes

The migration indexes created_at, method, status_code, user_id, duration_ms and has_slow_queries — the columns the dashboard filters and sorts on. The substring filters (path, route_name, ip_address) match with a leading wildcard and cannot use an index, so they are deliberately left unindexed.

Upgrading from 1.x? The has_slow_queries column and these indexes are part of the original migration, so an install that already migrated will not pick them up. Until the column exists, every insert fails and lands in the application log via the fallback path. CHANGELOG.md has the migration to run.

Artisan commands

Prune old logs

Deletes all log entries older than pruning.retain_days (default: 30 days). Schedule this command to keep your table from growing unbounded:

Publishing assets

Architecture

Both LaraScopeMiddleware and RequestLogger are bound as singletons so the same instance handles both handle() and terminate(). Per-request state ($collectedQueries, $shouldSkip) is reset at the top of every handle() call, making the package safe under persistent runtimes like Laravel Octane.