Forward output time_as_integer #1740
Merged
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
Signed-off-by: Davide Rossi <[email protected]>
Signed-off-by: Davide Rossi <[email protected]>
pepov
approved these changes
May 21, 2024
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.
This PR adds support for the time_as_integer configuration parameter to the Forward Output.
It inclused the addition of a simple test case for the Forward Output.
As specified in the fluentd 0.14 release notes ( https://www.fluentd.org/blog/fluentd-v0.14.0-has-been-released ), when this parameter is set to "true", the events are forwarded formatting the event time as an epoch integer, using second resolution.
If false, which is the default value, the events are sent as binary data with nanosecond resolution, which crashes old Fluentd versions.
In some occurrences, this settings can also be useful to forward events to Logstash instances,
because Logstash' "fluent" codec by default is not compatible with the nanosecond resolution binary data that comes from Fluentd.