Auto remove metric from registry #4
Merged
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
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.
When
autoResetis enabled for reporter, we used to reset metric to zero after it's collected. It will result inactive zero metrics hanging and accumulating, it does not make sense and even misleading to report those inactive ones again and again. Another drawback is, some kinds does not supportClear, so it's not consistent across kinds.So now we remove metric from registry after it being collected, instead. All kinds are consistent now, and inactive zero metrics will not reported again and again.
It should be noted, metric must be created dynamically with
GetOrRegisterto work withautoRemove. Otherwise the metric would never be registered after being removed.