-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Enable LoggingConfig configuration on Lambda Functions #12264
Comments
Looking at the documentation, it seems that defining LoggingConfig is a good idea. What about the following settings?
Can I please be assigned to this one? |
Whilst we're waiting for feedback, anyone who needs this functionality now can look towards: https://www.npmjs.com/package/serverless-logging-config |
Maybe the issue I opened over at #12284 should be folded into this one? It's asking for pretty much the same thing. When I wrote it, I honestly didn't even know it was a new feature. I just assumed everyone supported json through and through these days. |
Hey, this feature looks great and would allow us to reduce the cost. I have one question: shouldn't be there a possibility to set the LoggingConfig also on the provider level? Each Lambda probably is going to share the same configuration for logging, so it will reduce the boilerplate. |
Thank you for your input. We've implemented the requested feature in V.4, available for both Provider and Function settings. For the correct YAML usage, check out the |
Looks like that was just a documentation typo and the YAML implementation correctly uses camelCase. This feature is ready to go. |
Is there an existing issue for this?
Use case description
https://aws.amazon.com/blogs/compute/introducing-advanced-logging-controls-for-aws-lambda-functions/
Recently announced, would be nice to be able to configure
Proposed solution (optional)
No response
The text was updated successfully, but these errors were encountered: