fix(multiprocess): avoid double-building child metric names (#1035) #1146
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.
Description
Fixes #1035
Child metrics created via
labels()could rebuild their full names when using metric subclasses with defaultnamespace/subsystem/unit, especially in multiprocess mode, producing double-prefixed names.Problem
With a subclass like:
and an instance:
multiprocess mode could export child metrics with double-prefixed names like:
instead of the correct:
This happened because the already-built full name was passed to the child metric constructor, which then applied namespace/subsystem/unit transformations a second time.
Solution
In
MetricWrapperBase.__init__, store original constructor arguments:In
MetricWrapperBase.labels(), use stored values when creating child metrics:This ensures the full name is built exactly once, making single-process and multiprocess exports consistent.
Testing
getattr()fallbacksBreaking Changes
None (internal-only change to
MetricWrapperBase)