Fix timestamp in collected data, to be compliant with ISO8601 #2
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
DISCLAIMER: this update can break existing log processing chains, like the ELK stack. The logged timestamp is expected to be ISO8601 compliant, to be easy to parse with log processing chains. However, before this fix, the logged timestamp represented the *local time* and was not ISO8601 compliant. To solve this problem, this fix aims at logging a *UTC* timestamp, which is ISO8601 compliant. In other words, the collected timestamp is now less human readable and more processing chain friendly.
|
Sorry for the delay. |
|
Thanks :-) |
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.
DISCLAIMER: this update can break existing log processing chains, like the
ELK stack.
The logged timestamp is expected to be ISO8601 compliant, to be easy to
parse with log processing chains.
However, before this fix, the logged timestamp represented the local time
and was not ISO8601 compliant.
To solve this problem, this fix aims at logging a UTC timestamp, which is
ISO8601 compliant.
In other words, the collected timestamp is now less human readable and more
processing chain friendly.