How to Log INFO to a Separate File in Laravel

Overview of Laravel Logging System

Laravel, as a popular PHP framework, utilizes the Monolog library for flexible logging mechanisms. In practice, separating specific level logs into independent files enhances system maintainability and debugging efficiency. Based on Q&A data, this article focuses on technical solutions for storing INFO logs separately in Laravel 5.1 and later versions.

Specifying Log Files in Laravel 5.1

In Laravel 5.1, custom log file paths can be defined using the Log facade's useDailyFiles or useFiles methods. Key steps include: first, call Log::useDailyFiles(storage_path() . '/logs/info.log') to set the file path, which automatically creates log files with daily rotation; then, use Log::info('INFO level message content') to log messages. Example code:

Log::useDailyFiles(storage_path() . '/logs/info.log');
Log::info('Sample INFO log message, recorded to a separate file.');

Here, the first parameter of useDailyFiles specifies the file path, and the second optional parameter controls log retention days, defaulting to indefinite storage. This method integrates directly with Monolog handlers for efficient logging.

Log Channel Configuration in Laravel 5.6 and Above

Starting from Laravel 5.6, the logging system introduces channel concepts, allowing definition of multiple independent log configurations in the config/logging.php file. For example, add an INFO-specific channel:

'info_channel' => [
    'driver' => 'single',
    'path' => storage_path('logs/info.log'),
    'level' => 'debug',
],

After configuration, call via Log::channel('info_channel')->info('INFO message') to achieve log separation. This approach supports finer level control and driver extensions, recommended for modern Laravel projects.

Advanced Custom Logger Helper Implementation

For complex requirements, a custom Logger class can be built to dynamically manage multiple log channels based on Monolog. Example helper class encapsulates methods for each log level, such as:

public function info(string $channel, string $message, array $context = []): bool
{
    return this->log($channel, Logger::INFO, $message, $context);
}

Registered via a service provider for global access, this enhances flexibility and testability, suitable for scenarios requiring programmatic log management.

Technical Comparison and Best Practices Summary

Overall, the Laravel 5.1 method is suitable for quick implementation in legacy projects, while newer versions' log channels offer structured configuration. Recommendations: use useDailyFiles for 5.1 and channel configuration for 5.6+. Custom helpers serve as supplements for special needs. All methods rely on Monolog to ensure logging performance and compatibility.