{"id":637,"date":"2025-09-05T11:39:32","date_gmt":"2025-09-05T11:39:32","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=637"},"modified":"2025-09-05T11:39:34","modified_gmt":"2025-09-05T11:39:34","slug":"how-to-log-and-monitor-errors-in-laravel-with-monolog","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/how-to-log-and-monitor-errors-in-laravel-with-monolog\/","title":{"rendered":"How to Log and Monitor Errors in Laravel with Monolog"},"content":{"rendered":"\n

Error logging is one of the most important parts of maintaining a reliable Laravel application. While simple dd()<\/code> statements can help in development, production apps need structured, configurable, and persistent logs. Laravel uses Monolog<\/strong> under the hood, which is a powerful logging library that supports multiple channels, handlers, and integrations. In this article, we\u2019ll learn how to configure Monolog, log errors to different destinations, monitor logs in production, and apply best practices for scaling logging in real-world projects.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Laravel Logging Basics<\/strong><\/h2>\n\n\n\n

Laravel provides a unified Log<\/code> facade for writing logs. By default, logs are written to storage\/logs\/laravel.log<\/code>. The logging configuration is located in config\/logging.php<\/code> and defines channels like stack<\/code>, single<\/code>, daily<\/code>, slack<\/code>, and more.<\/p>\n\n\n

use<\/span> Illuminate<\/span>\\Support<\/span>\\Facades<\/span>\\Log<\/span>;\n\nLog::info('User visited dashboard.'<\/span>);\nLog::warning('Payment processing is slow.'<\/span>);\nLog::error('Unable to connect to database.'<\/span>);<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Each log entry has a level (info<\/code>, warning<\/code>, error<\/code>, critical<\/code>, etc.) defined by the RFC 5424 standard<\/a>. This helps filter logs when monitoring large systems.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Configuring Log Channels<\/strong><\/h2>\n\n\n\n
Channels define where and how logs are stored. Laravel supports multiple channels at once using the stack<\/code> driver. Common drivers include single<\/code> (one file), daily<\/code> (rotating logs), slack<\/code>, syslog<\/code>, and custom Monolog handlers.<\/p>\n\n\n
\/\/ config\/logging.php<\/span>\nreturn<\/span> [\n    'default'<\/span> => env('LOG_CHANNEL'<\/span>, 'stack'<\/span>),\n\n    'channels'<\/span> => [\n        'stack'<\/span> => [\n            'driver'<\/span> => 'stack'<\/span>,\n            'channels'<\/span> => ['daily'<\/span>, 'slack'<\/span>],\n        ],\n\n        'daily'<\/span> => [\n            'driver'<\/span> => 'daily'<\/span>,\n            'path'<\/span> => storage_path('logs\/laravel.log'<\/span>),\n            'level'<\/span> => 'debug'<\/span>,\n            'days'<\/span> => 14<\/span>,\n        ],\n\n        'slack'<\/span> => [\n            'driver'<\/span> => 'slack'<\/span>,\n            'url'<\/span> => env('LOG_SLACK_WEBHOOK_URL'<\/span>),\n            'level'<\/span> => 'critical'<\/span>,\n        ],\n    ],\n];<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This configuration sends all logs to daily files and sends critical<\/code> level errors to Slack. This way, developers are alerted instantly for severe issues, while other logs are stored for analysis.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Custom Monolog Handlers<\/strong><\/h2>\n\n\n\n
Sometimes you want to send logs to third-party services (like Logstash, Graylog, or CloudWatch). Laravel lets you define custom Monolog handlers by extending tap<\/code> in logging.php<\/code>.<\/p>\n\n\n
\/\/ app\/Logging\/CustomizeFormatter.php<\/span>\nnamespace<\/span> App<\/span>\\Logging<\/span>;\n\nuse<\/span> Monolog<\/span>\\Formatter<\/span>\\LineFormatter<\/span>;\n\nclass<\/span> CustomizeFormatter<\/span>\n<\/span>{\n    public<\/span> function<\/span> __invoke<\/span>($logger)<\/span>\n    <\/span>{\n        foreach<\/span> ($logger->getHandlers() as<\/span> $handler) {\n            $handler->setFormatter(new<\/span> LineFormatter(\n                \"[%datetime%] %channel%.%level_name%: %message% %context% %extra%\\n\"<\/span>\n            ));\n        }\n    }\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Then register it in config\/logging.php<\/code>:<\/p>\n\n\n
'daily'<\/span> => [\n    'driver'<\/span> => 'daily'<\/span>,\n    'path'<\/span> => storage_path('logs\/laravel.log'<\/span>),\n    'level'<\/span> => 'debug'<\/span>,\n    'days'<\/span> => 14<\/span>,\n    'tap'<\/span> => [App\\Logging\\CustomizeFormatter::class],\n],<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This allows you to format log messages consistently across all environments, making parsing easier for log aggregators.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Context and Structured Logging<\/strong><\/h2>\n\n\n\n
Logs become far more useful when you include structured context data, like user IDs, request IDs, or payloads.<\/p>\n\n\n
Log::error('Order failed to process.'<\/span>, [\n    'order_id'<\/span> => $order->id,\n    'user_id'<\/span> => $order->user_id,\n]);<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This context can be filtered in monitoring tools, making it easier to trace specific errors and build dashboards.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Monitoring Logs in Production<\/strong><\/h2>\n\n\n\n
For production, logs should be centralized and monitored. Common approaches include:<\/p>\n\n\n\n