[Prometheus Receiver] Add test cases to validate honor_timestamp #6705
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.
Description: Added new Prometheus Receiver test case to validate
honor_timestamp
functionality.TestHonorTimeStampsWithTrue
validates:Start_timestamp
is same aspoint_timestamp
, read from the explicit timestamp given to the datapoint in the testdata.Start_timestamp
should be the explicit timstamp of first-time you see a particular metricStart_timetsamp
should get reset if the current scrape has lower value than the previous scrapestart_timestamp
exhibit no issues in this test.TestHonorTimeStampsWithFalse
validates:honor_timestamp
config set to false, valid testdata provided with explicit timestamps does not get honoured.Link to tracking Issue:
Issue #6085
cc @alolita @Aneurysm9