fix(inputs.postgresql_extensible): Use same timestamp for each gather #15401
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
Rather than using a different timestamp for each query, this uses a single timestamp determined at the start of gather, for any and all metrics generated during that gather. While the timestamp might be off from when the actual queries are run, it combines all metrics around a single timestamp to better understand when data was captured. fixes: influxdata#9737
telegraf-tiger
bot
added
fix
|
Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
DStrand1
approved these changes
May 29, 2024
powersj
added
the
ready for final review
srebhan
approved these changes
May 31, 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.
Summary
Rather than using a different timestamp for each query, this uses a single timestamp determined at the start of gather, for any and all metrics generated during that gather.
While the timestamp might be off from when the actual queries are run, it combines all metrics around a single timestamp to better understand when data was captured.
Checklist
Related issues
fixes: #9737