A Laravel package that records exceptions to a database and sends notifications via multiple channels.
LERN is a Laravel package that captures exceptions in Laravel applications, records them to a database, and sends notifications via multiple channels like Email, Slack, and SMS. It helps developers monitor and debug errors in production by providing both persistent storage and real-time alerts.
Laravel developers and teams who need robust exception tracking and alerting for their applications, especially in production environments where quick error detection is critical.
Developers choose LERN for its seamless Laravel integration, flexible notification channels, and configurable data collection, offering a lightweight, open-source alternative to more complex error monitoring services.
LERN is a Laravel 5 package that will record exceptions into a database and will notify you via Email, Pushover or Slack.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates directly with Laravel's exception handler and uses Eloquent models for querying, as shown in the README with examples like ExceptionModel::orderBy() for easy access to recorded exceptions.
Supports multiple channels including Email, Slack, SMS via Twilio/Plivo, and Sentry through Monolog handlers, with configurable settings in lern.php for tailored alerts.
Allows selective collection of request details such as method, URL, user ID, and input data via the 'collect' array in config, enabling focused debugging without unnecessary bloat.
Enables custom Monolog handlers and dynamic log level adjustments programmatically, as demonstrated with LERN::setLogLevel() for fine-grained control over notifications.
Requires modifying app/Exceptions/Handler.php and running migrations, which adds overhead compared to drop-in services, and version migrations (e.g., 3.x to 4.x) can break compatibility.
Lacks built-in dashboards, error grouping, or performance monitoring; the roadmap only mentions adding more Monolog handlers, leaving gaps for teams needing comprehensive error insights.
Relies on a local database for storing exceptions, which can become a performance bottleneck in high-traffic applications and requires manual maintenance unlike cloud-based alternatives.