[lambda_logs] fix parsing failure when message is string#17398
Open
gpop63 wants to merge 2 commits intoelastic:mainfrom
Open
[lambda_logs] fix parsing failure when message is string#17398gpop63 wants to merge 2 commits intoelastic:mainfrom
message is string#17398gpop63 wants to merge 2 commits intoelastic:mainfrom
Conversation
gpop63
added
the
Team:Obs-InfraObs
Contributor
Author
|
/test |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
cc @gpop63 |
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
3 participants
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.
Proposed commit message
this PR fixes
lambda_logsparsing failure whenaws.lambda.messagereceives astringvalue instead of anobject.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots