Merge structured logging into dev in preparation for release #1803
Conversation
This file contains 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
Lambda JSON Exception handling and frame type
…gging. (#1795) The serialization is done as a best attempt with a fallback to using "ToString" if the reflection fails for NativeAOT.
* Fix issue with not correctly detecting "warning" log level. * Add integ test confirming JSON logging unhandled exception level
…ws-lambda-dotnet into feature/structured-logging
philasmar
approved these changes
Sep 4, 2024
96malhar
approved these changes
Sep 4, 2024
This was referenced Sep 19, 2024
Closed
1 task
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.
This PR merges the structured logging feature branch into dev in preparation for release. All commits have been reviewed in previous PR except the last PR which contains the version bumps.