Closed
Conversation
Member
|
Hi, have you been able to test these changes in Lambda? |
Author
|
Hi, the change works, in the sense that larger logs are exported intact from Lambda. The only thing is if some app is expecting log_limit to reduce their Cloudwatch (and $) usage. |
Member
|
Thanks! I've finally merged in v3: #304 |
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.
Hello!
I'm needing bigger logs, so I added a layer increasing the log_limit in my app.
But, since Cloudwatch now allows logs up to 256kb (https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/cloudwatch_limits_cwl.html), is there a chance this can be applied to the base layer?
Thanks from a fan!