Download the PHP package amjadiqbal/laravel-logpulse without Composer
On this page you can find all versions of the php package amjadiqbal/laravel-logpulse. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download amjadiqbal/laravel-logpulse
More information about amjadiqbal/laravel-logpulse
Files in amjadiqbal/laravel-logpulse
Package laravel-logpulse
Short Description Proactive log health monitoring & intelligent alerting for Laravel applications. Catch production issues before your customers do.
License MIT
Homepage https://github.com/AmjadIqbal/laravel-logpulse
Informations about the package laravel-logpulse
Installation โข Configuration โข Usage โข How it works
๐ค The Problem
Your production app is silently failing. A webhook endpoint returns 500 errors 200 times per hour. Your disk fills with logs. Your database connections exhaust. And you don't know until a customer complains.
Traditional log viewers are reactive โ you only see problems when you manually check.
โจ The Solution
LogPulse acts as a heartbeat monitor for your Laravel application. It listens to your logging engine in real-time, detects abnormal error patterns, and alerts you before your customers notice.
๐ Features
- โก Real-time error detection โ Catches error spikes as they happen
- ๐ฏ Intelligent threshold alerts โ Not just count, but pattern-based detection
- ๐ System Burden Score โ Understand the impact, not just the count
- ๐ Multi-channel notifications โ Slack, Discord, Email, SMS, Webhooks
- ๐ก๏ธ Self-protecting โ Circuit breaker prevents alert storms
- ๐ Adaptive baselines โ Learns your normal patterns (Pro)
- ๐จ Beautiful dashboard โ Built-in health monitoring UI
- ๐งช Simulation mode โ Test your alerts without waiting for real errors
- ๐ฎ Interactive CLI โ Laravel Prompts-powered installation wizard
- ๐ Ecosystem integration โ Works with Pulse, Horizon, Telescope
๐ฆ Installation
Guided setup (recommended):
Or non-interactively (CI/scripted installs):
Publish the config manually instead, if you'd rather configure by hand:
โ๏ธ Configuration
Everything lives in config/logpulse.php, driven by environment variables:
- Channels:
slack,discord,mail,webhook,vonage(SMS) โ any combination. - Thresholds: error count within a rolling time window, per severity (
critical/warning/info). - Presets:
saas-webhook,ecommerce,api-gateway,cms-blog, orcustomโ pre-tuned thresholds and pattern detection for common application shapes.logpulse:quickstartwalks you through picking one. - Dashboard: a built-in
/logpulseroute (behindweb+authmiddleware by default) showing live burden score, top errors, and circuit-breaker status.
๐ฅ๏ธ Usage
LogPulse listens to Laravel's own MessageLogged event automatically once installed โ no extra
wiring needed for Log::error()/Log::critical() calls to start feeding the dashboard and
alert pipeline.
๐ก๏ธ How alerting works
- Every logged error is aggregated by
(exception_class, route)into alogpulse_eventsrow, with anoccurrence_countrather than one row per occurrence. FrequencyAnalyzerchecks the rolling count against your configured thresholds.PatternMatcherlooks for higher-level patterns across recent events โ cascade failures (many different exceptions in a burst), retry storms (exponentially shortening intervals), dependency outages, resource exhaustion, and degraded performance.- A triggered alert goes out over your configured channels โ unless the circuit breaker for that channel is open, which caps how many alerts can fire per minute so a real incident doesn't also turn into an alert flood.
๐ License
MIT License. See LICENSE.md.
Changelog
See CHANGELOG.md.
Author
Amjad Iqbal โ amjad.com.pk ยท GitHub
All versions of laravel-logpulse with dependencies
laravel/framework Version ^9.0|^10.0|^11.0
laravel/prompts Version ^0.1.15
guzzlehttp/guzzle Version ^7.0