Adjust Timestamp Parsing #57
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
ricoberger
force-pushed
the
adjust-timestamp-parsing
branch
3 times, most recently
from
0bdb489
to
69d5cd2
Compare
Since Fluent Bit v2.1.0, the event format is represented as 2-element array with a nested array as the first element. The timestamp element is allocated in the first position of that nested array, so that the logic to get the timestamp must be adjusted.
ricoberger
force-pushed
the
adjust-timestamp-parsing
branch
from
69d5cd2
to
f1514d6
Compare
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.
Since Fluent Bit v2.1.0, the event format is represented as 2-element array with a nested array as the first element. The timestamp element is allocated in the first position of that nested array, so that the logic to get the timestamp must be adjusted.