Open
Conversation
trivenay
reviewed
Mar 11, 2026
f152901 to
04b46a4
Compare
04b46a4 to
6d392d3
Compare
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
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.
Description of changes:
Add structured logging support to the Ruby RIC on the
Loggerpath, consistent withthe structured logging behavior in other Lambda managed runtimes (Python, Node.js, etc.).
When
AWS_LAMBDA_LOG_FORMAT=JSON, each log output is a JSON object containingat least four key-value pairs:
timestamp– the time the log message was generated (ISO 8601, UTC)level– the log level assigned to the message (DEBUG, INFO, WARN, ERROR, FATAL)message– the contents of the log messagerequestId– the unique request ID for the function invocationThis PR includes the following changes:
LoggerpathAWS_LAMBDA_LOG_FORMATandAWS_LAMBDA_LOG_LEVELTarget (OCI, Managed Runtime, both):
Both
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Example Usage:
Output without
AWS_LAMBDA_LOG_FORMAT:I, [2026-03-10T22:30:46.745494 #16] INFO 3244ba10-b213-4742-9cbc-fcc611f42625 -- : Inside the handler functionOutput with
AWS_LAMBDA_LOG_FORMAT=JSON:{ "timestamp":"2026-03-10T21:37:36.350555Z", "level":"INFO", "message":"Inside the handler function", "requestId":"d1491d62-2ed4-4d08-a1be-feea698100f7" }