fix(logs): normalize logs timestamp format with fixed sub-second digits #1387
Conversation
This file contains hidden or 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
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.
During the configuration of the log forwarding service in Warpgate and the subsequent processing of messages, I noticed that the timestamp format received is inconsistent. In some cases, the data is sent in milliseconds, and in others, in nanoseconds.
According to the
chronolibrary documentation,to_rfc3339method uses theAutoSiformat by default, which means it automatically selects one of Secs, Millis, Micros, or Nanos to display all available non-zero sub-second digits. More info here.This can lead to processing issues in systems that expect a fixed layout (e.g., Telegraf). To resolve this, the function call should be changed to
to_rfc3339_opts, passing a fixed format of nanoseconds.