This repository has been archived by the owner on Sep 21, 2023. It is now read-only.
Add custom event encoder for Elasticsearch output #277
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
Event
type along with the fastjson implementation in order to correctly add a@timestamp
field 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
@timestamp
field.Checklist
CHANGELOG.md
orCHANGELOG-developer.md
.