Cherry-pick #15847 to 7.6: Use RFC3339 format for timestamps in SQL module #15856
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
This way timezone and more precise information is stored in the final events in case they are lately parsed as dates. (cherry picked from commit 121f19d)
ChrsMark
approved these changes
Jan 27, 2020
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.
Cherry-pick of PR #15847 to 7.6 branch. Original message:
What does this PR do?
Format timestamps collected with the SQL module using the RFC3339 Nano format,
that includes the timezone and is a more precise representation.
Why is it important?
So timezone information and precission is not lost when formatting the timestamps
for the final event.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration files