.: Add a multi incarnation scope wrapper #7
Merged
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 does this PR do?
In an effort to find potential contention in our infrastructure i have been instrumenting different pools (connection pool to the DB, thrift client pool...).
One issue arise in that kind of scenario, if there is multiple pool with similar labels it makes the data worth less to be analyzed.
This
stats.Scopewrapper automatically add aincarnationlabel that is incremented. So if two connection pool to the DB are opened metrics for both will be reported independently.What are the observable changes?
Good PR checklist
Additional Notes