Report never-set gauges in mostrecent multiprocess mode#1193
Open
sean-kim05 wants to merge 1 commit into
Open
Conversation
In the mostrecent/livemostrecent accumulation branch, sample_timestamps is a defaultdict(float), so the stored timestamp of a series defaults to 0.0. A gauge child that was created but never set() also has a stored timestamp of 0, so the strict 'current_timestamp < timestamp' check was never satisfied and the series was dropped from collection entirely. Every other gauge mode (sum, min, max, all) reports such a child as 0, so mostrecent silently omitting it was inconsistent. Register the sample when it is first seen, regardless of timestamp, and still let a strictly newer timestamp win afterwards. Add test_gauge_mostrecent_never_set, asserting a mostrecent gauge that is created but never set is reported as 0 rather than missing. Signed-off-by: Sean Kim <skim8705@gmail.com>
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
1 participant
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.
In the mostrecent/livemostrecent accumulation branch, sample_timestamps
is a defaultdict(float), so the stored timestamp of a series defaults to
0.0. A gauge child that was created but never set() also has a stored
timestamp of 0, so the strict 'current_timestamp < timestamp' check was
never satisfied and the series was dropped from collection entirely.
Every other gauge mode (sum, min, max, all) reports such a child as 0,
so mostrecent silently omitting it was inconsistent. Register the sample
when it is first seen, regardless of timestamp, and still let a strictly
newer timestamp win afterwards.
Add test_gauge_mostrecent_never_set, asserting a mostrecent gauge that is
created but never set is reported as 0 rather than missing.
@csmarchbanks