Enhance cortex_ingester_inflight_push_requests metric#6437
Merged
alanprot merged 1 commit intocortexproject:masterfrom Dec 18, 2024
Merged
Conversation
Signed-off-by: alanprot <alanprot@gmail.com>
danielblando
approved these changes
Dec 18, 2024
Member
|
LGTM! |
SungJin1212
approved these changes
Dec 18, 2024
3 tasks
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
3 participants
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.
What this PR does:
The cortex_ingester_inflight_push_requests metric currently monitors the inflightPushRequests atomic integer directly.
This approach can be misleading, as the value fluctuates significantly and only represents the exact value at the time of scraping.
This PR modifies the metric to report the maximum number of concurrent requests observed within each one-minute interval.
I think is fine changing this metric (instead of creating a new one) as the intent was always the same.
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]