fix: Initialize metrics first among telemetry subsystems#193
Merged
Conversation
Other subsystems may register metrics during initialization (specifically, `tracing_max_queue_size` right now). Not initializing metrics first causes the `REGISTRIES` singleton to be defaulted when a metric is registered beforehand.
fisherdarling
approved these changes
Apr 9, 2026
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.
Other subsystems may register metrics during initialization
(specifically,
tracing_max_queue_sizeright now). Not initializingmetrics first causes the
REGISTRIESsingleton to be defaulted when ametric is registered beforehand.
Includes release commit for v5.6.1