Download the PHP package webimpian/laravel-log-central without Composer

Laravel Log Central

Ship exceptions, log entries, and API request metrics from any Laravel application to a Log Central server. Install the package, set a few environment variables, and telemetry flows automatically over queued, batched background jobs — no code changes required.

Highlights

• Automatic exception tracking — every reported exception (web, queue, Artisan, scheduler, or an explicit report($e)) is shipped with its fingerprint, stack trace, request context, and authenticated user.
• Centralised log channels — nominate the channels you care about (or * for all); their entries stream to Log Central while your local log files keep working unchanged.
• Zero-touch API monitoring — every api/* request is recorded with its method, route, status, and duration, plus the scrubbed response and payload, DB query count and time, peak memory, user-agent, and the authenticated user. Captured after the response is sent, so request latency is never affected.
• Non-blocking by design — all telemetry is dispatched to queued jobs, batched, and retried with capped backoff. Delivery failures are handled silently and can never loop or disrupt the host application.
• Sensitive data scrubbed at the source — passwords, tokens, keys, and card numbers are replaced with [scrubbed] before anything leaves your application.

Requirements

• PHP 7.4 or higher
• Laravel 6, 7, 8, 9, 10, 11, 12, or 13
• guzzlehttp/guzzle on Laravel 6 only, which ships no HTTP client of its own
• A running queue worker (Redis / Horizon recommended)
• A Log Central project key — create an app on the dashboard to obtain one

Installation

Add the connection details to your .env:

API monitoring is enabled by default for api/*. The following are optional — use them to narrow the monitored paths or control what is stored:

The service provider registers itself automatically — no further wiring is required.

On Laravel 6, also install an HTTP client, which the framework does not provide until 7.0:

Configuration

Publish the configuration file to customise scrub keys, the shipping queue, or defaults:

Shipping only happens when CENTRAL_LOG_ENABLED is true and both the URL and token are set. With anything missing the package stays completely dormant — no middleware, no listeners, no channel changes.

How it works

• Log channels are wrapped, not replaced. Each nominated channel is renamed to <name>_local and a stack of [<name>_local, central] takes its place, so your existing files, Slack channels, or Papertrail sinks keep working exactly as before. The central and emergency channels are never wrapped, and neither are channels that are already stacks. Under *, discard sinks (null and NullHandler-backed channels) are skipped too — they exist to throw entries away, so the wildcard must not resurrect them.
• Entries are buffered, then batched. Log rows and API records accumulate in memory (up to 200) and flush as a single queued job when the app terminates or the process shuts down — one job per batch, not one per entry.
• API requests are recorded during terminate(), after the response has been sent, so nothing here adds latency to the request itself.
• Delivery is retried, then given up quietly. A transient failure (connection error, 5xx, 408, 429) is retried up to 3 times with a 10s then 60s backoff, and dropped in silence if it never succeeds — telemetry must never disturb the host app. Anything else (a bad URL, a rejected token) cannot be fixed by retrying, so the job is failed loudly and lands in failed_jobs where you will see it.
• The shipper never reports itself. Exceptions thrown inside the package are filtered out before dispatch, so a broken Log Central can't loop telemetry back into itself.
• Oversized fields are capped. Any single field over 256 KB is replaced with a marker plus a 16 KB preview; API response and payload bodies are truncated to 4 KB.

What gets captured

Scrubbing sensitive data

Request input, log context, API payloads, and API responses are all filtered before anything leaves the application. Keys are matched case-insensitively and as substrings, so card also covers card_number and CardHolder.

Defaults: password, password_confirmation, current_password, token, api_key, apikey, secret, authorization, card, cvv, cvc, pin.

Publish the config and edit the scrub array to add your own — replacing the list, so keep the defaults you still want:

File uploads are never included in a payload.

Verifying the integration

The entry should appear on the Log Central dashboard within a few seconds. If it does not, work through the table below.

Troubleshooting

Compatibility

The ingest contract is frozen at v1.0 — any package version talks to any Log Central server.

Testing

License

The MIT License (MIT). See LICENSE.md for details.