Including Exception and EventId in Lambda Logger messages #401
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
|
Thanks for the PR. I'll take a look |
|
This was released as version 2.2.0 of Amazon.Lambda.Logging.AspNetCore. Thangs again for the PR. |
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.
Issue #, if available:
Microsoft.Extensions.Logging interface supports logging EventId and Exceptions, but when LambdaLogger is configured, those objects are not saved in CloudWatch.
Sample scenario:
The natural expectation is that both Logging Event and Exception will be available in CloudWatch, which is not the case.
Description of changes:
I've included 2 new settings on Lambda Logger Options to enable EventId and Exceptions logging.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.