Log event size increased to the latest vale#4
Merged
markinjapan merged 1 commit intophpnexus:masterfrom Jun 13, 2025
Merged
Conversation
markinjapan
approved these changes
Jun 13, 2025
Contributor
markinjapan
left a comment
markinjapan
left a comment
There was a problem hiding this comment.
Thanks for finding that!
Contributor
Author
|
Thank you for publishing this. And I found another commit of yours that filled in the gaps in my fix. Thanks for the follow! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
The April 2025 AWS update raised the upper limit of log event size. In this pull request, we will update our library to update the size that can be sent to the latest value.
What is the current behavior? (You can also link to an open issue here)
Previously it was 256K including reserved areas.
What is the new behavior (if this is a feature change)?
I increased it to 1MB.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
There are no breaking changes.
Other information:
https://aws.amazon.com/about-aws/whats-new/2025/04/amazon-cloudwatch-logs-increases-log-event-size-1-mb/
https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/cloudwatch_limits_cwl.html