feat: add ClearRegistry endpoint to clear all metrics immediately - #752
Closed
AruneshDwivedi wants to merge 1 commit into
Closed
feat: add ClearRegistry endpoint to clear all metrics immediately#752AruneshDwivedi wants to merge 1 commit into
AruneshDwivedi wants to merge 1 commit into
Conversation
Signed-off-by: Arunesh Dwivedi <arunesh.devops@gmail.com>
Contributor
|
We already have #747 which is working on that, I would rather work with that first for now. |
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
2 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.
Fixes #637
Adds a ClearRegistry method to the Registry interface that immediately removes
all registered metrics. This allows users to clear the metric registry without
quitting the exporter.
Use case: When working with large clusters of statsd_exporter where the number
of instances changes or order changes, metrics distribution keys change due to
hashing on statsrelay. Users need a way to immediately forget accumulated
metrics and start collecting in a new distribution.
This is different from /-/reload (metrics persist) and /-/quit (disruptive).