Feature
Centralised application logs for Laravel
Your Laravel logs shipped as they happen, searchable by level and environment, and attached to the exception they surround.
Turning it on, one variable
MONITOR_LOGS_ENABLED=true
The problem
Logs live on the server, in a file nobody reads before the incident. The day you need them you need a connection, the right path, and a grep through several gigabytes while the customer waits.
What you get
- Search by level, environment, channel and period
- A seven-day severity timeline, so a spike shows without being looked for
- The logs from five minutes either side of an exception, on that exception's page
- Structured context shown as it is, without flattening your arrays
- Your plan's retention applied on its own, with no purge to write
- End-to-end encryption as an option, decrypted in your browser
How it works
01
A hook, not a rewrite
The client package hooks the framework's own logging, Laravel's log events or a Monolog handler on Symfony. Your existing calls ship as they are, without you touching a line.
02
Batched, never inside the request
Lines are buffered and sent when the request or the job ends. Your application's latency does not depend on ours.
03
Filtered before they leave
Sensitive keys are masked by name, and anything shaped like an email, an IBAN or a card is masked by shape, wherever it sits.