Categories

How LEXO's Log Monitor Package Simplifies Error Tracking and Debugging

Donate with

82uymVXLkvVbB4c4JpTd1tYm1yj1cKPKR2wqmw3XF8YXKTmY7JrTriP4pVwp2EJYBnCFdXhLq4zfFA6ic7VAWCFX5wfQbCC

Copy Monero Donation Address

Donate with

Donate BAT now

Verified BAT publisher

LEXO Laravel Log Monitor

In the fast-paced world of web development, staying on top of application errors can mean the difference between a smooth user experience and frustrated customers. For Laravel developers, log files are a critical yet often underutilized resource for maintaining application health. The Laravel Log Monitor package by LEXO GmbH transforms these cryptic log files into actionable insights, helping you identify and resolve issues before they impact your users.

Why Monitoring Logs Matters in Laravel Applications

Laravel's robust logging system captures a wealth of information about your application's performance and errors. However, manually sifting through these logs is time-consuming and inefficient. Important error patterns can easily go unnoticed until they escalate into major problems.

Consider these common scenarios:

• Your production application throws critical errors during non-working hours
• Intermittent issues occur that are difficult to reproduce in development
• Security vulnerabilities create suspicious patterns in your logs
• Performance bottlenecks gradually degrade user experience

Without proper monitoring, these issues can persist for days or even weeks before being addressed. The Laravel Log Monitor package solves this problem by providing automated monitoring and alerting for your application logs.

Introducing Laravel Log Monitor by LEXO GmbH

The Laravel Log Monitor package is an open-source solution developed by LEXO GmbH that seamlessly integrates with Laravel's existing logging system. Its primary purpose is to monitor your application's log files and send notifications when predefined error thresholds are exceeded. Notifications can be sent to Mattermost adn/or E-Mail.

Key Features and Benefits

• Automated Email Notifications: Receive timely alerts when errors occur, enabling rapid response to critical issues
• Customizable Error Thresholds: Configure monitoring sensitivity based on your application's specific needs
• Simple Integration: Works with Laravel's standard logging practices without requiring changes to your existing setup
• Pattern Exclusions: Filter out known or irrelevant errors to reduce notification noise
• Resource Efficiency: Lightweight implementation that won't impact your application's performance

By implementing Laravel Log Monitor, you'll transform your passive log files into an active monitoring system that keeps you informed about your application's health.

Installation

Link to GitHub page of LEXO Laravel Log Monitor.

First, you'll need to install the package via Composer:

composer require lexo/laravel-log-monitor

After installation, you can optionally publish the configuration file:

php artisan vendor:publish --tag=laravel-log-monitor-config

This will create a config/log-monitor.php file where you can customize the package's behavior.

Configure the package by adding these variables to your .env file:

LARAVEL_LOG_MONITOR_ENABLED=true

# Environments where monitoring is active (comma-separated)
LARAVEL_LOG_MONITOR_ENVIRONMENTS=production,local

# Mattermost integration settings
LARAVEL_LOG_MONITOR_MATTERMOST_URL=https://your-mattermost-url.tld
LARAVEL_LOG_MONITOR_MATTERMOST_TOKEN=your-mattermost-token
LARAVEL_LOG_MONITOR_MATTERMOST_CHANNEL=mattermost-channel-id

# Email notification recipients (comma-separated)
LARAVEL_LOG_MONITOR_EMAIL_RECIPIENTS=email1@website.tld,email2@website.tld

By default:

Only the production environment is monitored. Email notifications serve as a backup if Mattermost notifications fail.

To enable simultaneous Mattermost and email notifications, set in .env file:

LARAVEL_LOG_MONITOR_EMAIL_SEND_AS_BACKUP=false

The complete list of configuration options is available in the config file.

You can set Mattermost notification priority using the llm context key in your log messages:

Log::critical('test error', [
    'llm' => [
        'priority' => 'important',
        'alert' => true
    ],
    'something' => 'else'
]);

Notes:

• Logs of error type are always monitored by default
• Other log types can be included by adding 'alert' => true in the llm context
• Priority can be set to important or urgent.

Publish the configuration file to customize settings:

php artisan vendor:publish --tag=laravel-log-monitor-config

Customize the notification templates by publishing the view files:

php artisan vendor:publish --tag=laravel-log-monitor-views-email

Customize the notification templates by publishing the view files:

php artisan vendor:publish --tag=laravel-log-monitor-views-mattermost