Add raw JSON to event.original if parsing fails #9361
Closed
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
kvch
added
review
Filebeat
kvch
force-pushed
the
feature-filebeat-add-raw-msg-in-case-of-error
branch
from
68ffa4d to
704c5fa
Compare
|
@kvch I just want to clarify a thing, IIRC the current behavior on error is to take the If the above description is true, what are the advantages or copying the field to the |
|
Indeed. In hindsight, I have no idea why I have opened this PR. Closing. |
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.
If parsing a JSON message fails Filebeat adds
"error"key with the error returned by Go. This PR adds the raw message to help debugging.Inspired by #9172