{"id":642,"date":"2025-09-05T11:42:16","date_gmt":"2025-09-05T11:42:16","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=642"},"modified":"2025-09-05T11:42:18","modified_gmt":"2025-09-05T11:42:18","slug":"advanced-logging-and-monitoring-in-laravel-with-monolog","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/advanced-logging-and-monitoring-in-laravel-with-monolog\/","title":{"rendered":"Advanced Logging and Monitoring in Laravel with Monolog"},"content":{"rendered":"\n

In the previous article<\/a>, we covered the basics of logging with Monolog in Laravel. Now, let\u2019s go deeper into advanced logging and monitoring strategies. In large-scale projects, simply writing logs to files is not enough. You need structured logs, log rotation, external storage, and integration with observability platforms. In this article, we\u2019ll configure Monolog for production-ready logging, integrate with services like AWS CloudWatch, explore asynchronous logging, and apply best practices for scaling.<\/p>\n\n\n\n

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

Advanced Log Channels<\/strong><\/h2>\n\n\n\n

Laravel supports multiple channels combined in a stack. You can mix daily<\/code> logs with cloud-based services and instant alerts. Let\u2019s look at a custom stack<\/code> channel that combines multiple destinations:<\/p>\n\n\n

\/\/ config\/logging.php<\/span>\n'channels'<\/span> => [\n    'stack'<\/span> => [\n        'driver'<\/span> => 'stack'<\/span>,\n        'channels'<\/span> => ['daily'<\/span>, 'slack'<\/span>, 'cloudwatch'<\/span>],\n        'ignore_exceptions'<\/span> => false<\/span>,\n    ],\n\n    'cloudwatch'<\/span> => [\n        'driver'<\/span> => 'monolog'<\/span>,\n        'handler'<\/span> => Monolog\\Handler\\StreamHandler::class,\n        'with'<\/span> => [\n            'stream'<\/span> => 'php:\/\/stdout'<\/span>,\n        ],\n        'formatter'<\/span> => Monolog\\Formatter\\JsonFormatter::class,\n    ],\n],<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This setup logs daily to disk, sends critical alerts to Slack, and streams JSON logs to AWS CloudWatch. The JSON format is preferred for production because it integrates better with log aggregators.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Asynchronous Logging with Queues<\/strong><\/h2>\n\n\n\n
Heavy logging can slow down requests. To reduce impact, send logs asynchronously using Laravel\u2019s queue system. Here\u2019s how you can wrap logging inside a job:<\/p>\n\n\n
\/\/ app\/Jobs\/AsyncLog.php<\/span>\nnamespace<\/span> App<\/span>\\Jobs<\/span>;\n\nuse<\/span> Illuminate<\/span>\\Support<\/span>\\Facades<\/span>\\Log<\/span>;\n\nclass<\/span> AsyncLog<\/span> extends<\/span> Job<\/span>\n<\/span>{\n    public<\/span> $message;\n    public<\/span> $level;\n    public<\/span> $context;\n\n    public<\/span> function<\/span> __construct<\/span>($message, $level = 'info'<\/span>, $context = [])<\/span>\n    <\/span>{\n        $this<\/span>->message = $message;\n        $this<\/span>->level = $level;\n        $this<\/span>->context = $context;\n    }\n\n    public<\/span> function<\/span> handle<\/span>()<\/span>: void<\/span>\n    <\/span>{\n        Log::{$this<\/span>->level}($this<\/span>->message, $this<\/span>->context);\n    }\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Dispatch logs asynchronously:<\/p>\n\n\n
dispatch(new<\/span> \\App\\Jobs\\AsyncLog(\n    'Payment gateway timeout'<\/span>,\n    'error'<\/span>,\n    ['order_id'<\/span> => 1234<\/span>]\n));<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This allows logs to be processed in the background, keeping API responses fast while still persisting errors for monitoring.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Integrating with AWS CloudWatch<\/strong><\/h2>\n\n\n\n
For apps hosted on AWS, it\u2019s best to send logs directly to CloudWatch<\/strong>. This provides centralized storage, metrics, and alerts. Install the CloudWatch Monolog driver:<\/p>\n\n\n
composer require maxbanton\/cwh<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
Then configure the channel:<\/p>\n\n\n
\/\/ config\/logging.php<\/span>\n'cloudwatch'<\/span> => [\n    'driver'<\/span> => 'monolog'<\/span>,\n    'handler'<\/span> => Maxbanton\\Cwh\\Handler\\CloudWatch::class,\n    'with'<\/span> => [\n        'group'<\/span> => env('CLOUDWATCH_GROUP'<\/span>, 'laravel-app'<\/span>),\n        'stream'<\/span> => env('CLOUDWATCH_STREAM'<\/span>, 'production'<\/span>),\n        'retention'<\/span> => 14<\/span>,\n    ],\n],<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Now all logs will appear in the CloudWatch console where you can create alarms for error spikes or unusual activity.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Centralized Log Aggregation<\/strong><\/h2>\n\n\n\n
In microservices or multi-server environments, centralizing logs is essential. Common solutions include:<\/p>\n\n\n\n