This repository was archived by the owner on Sep 21, 2023. It is now read-only.
Add custom event encoder for Elasticsearch output #277
Merged
fearful-symmetry merged 3 commits intoelastic:mainfrom Mar 2, 2023
Merged
Add custom event encoder for Elasticsearch output #277fearful-symmetry merged 3 commits intoelastic:mainfrom
fearful-symmetry merged 3 commits intoelastic:mainfrom
Conversation
Contributor
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Contributor
Contributor
Author
|
/test |
1 similar comment
Contributor
Author
|
/test |
leehinman
approved these changes
Mar 2, 2023
faec
approved these changes
Mar 2, 2023
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does this PR do?
Fixes #256
Fixes #253
This adds a custom
Eventtype along with the fastjson implementation in order to correctly add a@timestampfield to events. This is something the Beats elasticsearch output already does, and presumably went unnoticed as the logic is buried in a special little encoder callback.Why is it important?
We need a
@timestampfield.Checklist
CHANGELOG.mdorCHANGELOG-developer.md.