-
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
Support json logging in Lambda #12284
Comments
+1 |
1 task
Probably could be folded into #12264 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Use case description
JSON logging is widely considered the standard way to emit log information. Especially to logging search and aggregation systems based on the ELK stack. We rely heavily on detailed logging information in order to understand and troubleshoot errors that happen during our rather large/intricate batch process. Having the ability to include "more than a string" of data is crucial for us. We emit our Python logs in json format using the AWS Powertools log formatter. We have configured our Cloud Watch Subscription Filters to read and pipe json formatted data to AWS Open Search. But we discovered that there was another setting for the Lambda itself that is set to Plain Text by default. We would like it if we could emit all our logs in JSON format.
Proposed solution (optional)
Support LoggingConfiguration options for Lambdas. Enable
json
by default since it is the (other) commonly accepted format by most logging systems. It is also going to be the default in aws as of Jan 1.The text was updated successfully, but these errors were encountered: