starred/monolog

Fork 0

mirror of https://github.com/Seldaek/monolog.git synced 2026-04-26 08:05:53 +03:00

[GH-ISSUE #1890] Truncated JsonFormatter logs at 8191 characters #809

New issue

Closed

opened 2026-03-04 02:18:13 +03:00 by kerem · 7 comments

kerem commented

2026-03-04 02:18:13 +03:00

Owner

Originally created by @Mad4T on GitHub (May 21, 2024).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/1890

version
Monolog version: 3.0
Laravel: 10.0

Issue Description:
We're encountering log truncation at 8191 characters within our Laravel application deployed on AWS ECS. CloudWatch logs from this specific app are affected, while logs from other apps function normally.
We suspect a potential limitation within Monolog (version 3.0) might be causing this behavior.

Expected Behavior:
We expect CloudWatch logs from our Laravel app to be captured in their entirety without truncation.

Code Snippet (relevant part of logger.php):
'stderr' => [ 'driver' => 'monolog', 'handler' => StreamHandler::class, 'formatter' => env('LOG_STDERR_FORMATTER'), 'with' => [ 'stream' => 'php://stderr', ], ]

Originally created by @Mad4T on GitHub (May 21, 2024). Original GitHub issue: https://github.com/Seldaek/monolog/issues/1890 **version** Monolog version: 3.0 Laravel: 10.0 **Issue Description:** We're encountering log truncation at 8191 characters within our Laravel application deployed on AWS ECS. CloudWatch logs from this specific app are affected, while logs from other apps function normally. We suspect a potential limitation within Monolog (version 3.0) might be causing this behavior. **Expected Behavior:** We expect CloudWatch logs from our Laravel app to be captured in their entirety without truncation. **Code Snippet (relevant part of logger.php):** `'stderr' => [ 'driver' => 'monolog', 'handler' => StreamHandler::class, 'formatter' => env('LOG_STDERR_FORMATTER'), 'with' => [ 'stream' => 'php://stderr', ], ]`

kerem

2026-03-04 02:18:13 +03:00

closed this issue
added the
Support
label

kerem commented

2026-03-04 03:00:51 +03:00

Author

Owner

@Seldaek commented on GitHub (Jun 28, 2024):

AFAIK there is no such limit in Monolog itself, but I am not very familiar with ECS and there might be something else there.

@Seldaek commented on GitHub (Jun 28, 2024): AFAIK there is no such limit in Monolog itself, but I am not very familiar with ECS and there might be something else there.

kerem commented

2026-03-04 03:00:51 +03:00

Author

Owner

@Mad4T commented on GitHub (Jun 30, 2024):

Issue happens in ECS and EKS. Also worth noting that logs from none php apps are not truncated.

@Mad4T commented on GitHub (Jun 30, 2024): Issue happens in ECS and EKS. Also worth noting that logs from none php apps are not truncated.

kerem commented

2026-03-04 03:00:51 +03:00

Author

Owner

@Seldaek commented on GitHub (Jul 6, 2024):

Yeah sorry but that's something you'll have to debug yourself I am afraid.. There is too much environment specific stuff at play here for me to help much.

@Seldaek commented on GitHub (Jul 6, 2024): Yeah sorry but that's something you'll have to debug yourself I am afraid.. There is too much environment specific stuff at play here for me to help much.

kerem commented

2026-03-04 03:00:51 +03:00

Author

Owner

@Seldaek commented on GitHub (Jul 11, 2024):

If you figure it out please share here, it may help someone else one day

@Seldaek commented on GitHub (Jul 11, 2024): If you figure it out please share here, it may help someone else one day

kerem commented

2026-03-04 03:00:51 +03:00

Author

Owner

@Mad4T commented on GitHub (Jul 14, 2024):

if we ever find the reason will post it here, but we ended up doing a workaround to truncate the logs using Processor :

<?php

namespace App\Logging;

use Monolog\LogRecord;
use Monolog\Processor\ProcessorInterface;
use Throwable;

class TruncateStackTraceProcessor implements ProcessorInterface
{
    private int $traceLimit;

    public function __construct(int $traceLimit = 30)
    {
        $this->traceLimit = $traceLimit;
    }

    public function __invoke(LogRecord $record): LogRecord
    {
        $context = $record->context;
        if (isset($context['exception']) && $context['exception'] instanceof Throwable) {
            $exception = $record['context']['exception'];
            $trace = $exception->getTrace();

            if (count($trace) > $this->traceLimit) {
                $trace = array_slice($trace, 0, $this->traceLimit);
            }

            $context['exception'] = [
                'class' => get_class($record['context']['exception']),
                'message' => $record['context']['exception']->getMessage(),
                'code' => $record['context']['exception']->getCode(),
                'file' => $record['context']['exception']->getFile() . ':' . $record['context']['exception']->getLine(),
                'trace' => $this->formatStacktrace($trace),
            ];

            $record = $record->with(context: $context);
        }

        return $record;
    }

    private function formatStacktrace(array $trace): string {
        return collect($trace)
            ->map(function ($el) {
                $file = $el['file'] ?? '[unknown]';
                $line = $el['line'] ?? '[unknown]';
                $class = $el['class'] ?? '[unknown]';
                $function = $el['function'] ?? '[unknown]';
                $type = $el['type'] ?? '->';
                return "at {$class}{$type}{$function} ({$file}:{$line})";
            })
            ->join("\n");
    }
}

@Mad4T commented on GitHub (Jul 14, 2024): if we ever find the reason will post it here, but we ended up doing a workaround to truncate the logs using Processor : ``` <?php namespace App\Logging; use Monolog\LogRecord; use Monolog\Processor\ProcessorInterface; use Throwable; class TruncateStackTraceProcessor implements ProcessorInterface { private int $traceLimit; public function __construct(int $traceLimit = 30) { $this->traceLimit = $traceLimit; } public function __invoke(LogRecord $record): LogRecord { $context = $record->context; if (isset($context['exception']) && $context['exception'] instanceof Throwable) { $exception = $record['context']['exception']; $trace = $exception->getTrace(); if (count($trace) > $this->traceLimit) { $trace = array_slice($trace, 0, $this->traceLimit); } $context['exception'] = [ 'class' => get_class($record['context']['exception']), 'message' => $record['context']['exception']->getMessage(), 'code' => $record['context']['exception']->getCode(), 'file' => $record['context']['exception']->getFile() . ':' . $record['context']['exception']->getLine(), 'trace' => $this->formatStacktrace($trace), ]; $record = $record->with(context: $context); } return $record; } private function formatStacktrace(array $trace): string { return collect($trace) ->map(function ($el) { $file = $el['file'] ?? '[unknown]'; $line = $el['line'] ?? '[unknown]'; $class = $el['class'] ?? '[unknown]'; $function = $el['function'] ?? '[unknown]'; $type = $el['type'] ?? '->'; return "at {$class}{$type}{$function} ({$file}:{$line})"; }) ->join("\n"); } } ```

kerem commented

2026-03-04 03:00:51 +03:00

Author

Owner

@sc0rp10 commented on GitHub (Apr 2, 2025):

@Mad4T please take a look to log_limit setting of php-fpm: it was the key to solving a similar problem in my case (I'm writing this mostly for folks from google).

@Seldaek It would be great if you added this information to the readme, very difficult to find the cause of this truncation.

@sc0rp10 commented on GitHub (Apr 2, 2025): @Mad4T please take a look to [log_limit](https://www.php.net/manual/en/install.fpm.configuration.php#log-limit) setting of php-fpm: it was the key to solving a similar problem in my case (I'm writing this mostly for folks from google). @Seldaek It would be great if you added this information to the readme, very difficult to find the cause of this truncation.

kerem commented

2026-03-04 03:00:52 +03:00

Author

Owner

@Seldaek commented on GitHub (Apr 2, 2025):

Feel free to send a PR if you have a good understanding of the problem because I have zero context here so it'll take me much more effort and probably not get done..

@Seldaek commented on GitHub (Apr 2, 2025): Feel free to send a PR if you have a good understanding of the problem because I have zero context here so it'll take me much more effort and probably not get done..

kerem referenced this issue

2026-03-04 03:10:46 +03:00

[PR #809] [CLOSED] Feature/composer update #1360