-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Truncated JsonFormatter logs at 8191 characters #1890
Comments
AFAIK there is no such limit in Monolog itself, but I am not very familiar with ECS and there might be something else there. |
Issue happens in ECS and EKS. Also worth noting that logs from none php apps are not truncated. |
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. |
If you figure it out please share here, it may help someone else one day |
if we ever find the reason will post it here, but we ended up doing a workaround to truncate the logs using Processor :
|
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', ], ]
The text was updated successfully, but these errors were encountered: