Repository navigation
Conversation
The runtime-wide `tokio_runtime_core_parked_workers` gauge counts workers with odd Tokio park/unpark counters at each sample. It uses the existing runtime labels and monitoring path without runtime hooks. The gauge excludes blocking-pool threads and represents independently sampled workers rather than an atomic runtime-wide snapshot.
cbranch
approved these changes
Nov 17, 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
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.
The Tokio runtime monitor now exposes
tokio_runtime_core_parked_workers, an aggregate gauge derived from workers whoseRuntimeMetrics::worker_park_unpark_count()is odd at each sample. It reuses the existing runtime registration, sampling, and optionalruntime_nameandruntime_idlabels without installing runtime hooks.The gauge excludes blocking-pool threads and remains unchanged between samples. Workers are read independently, so the aggregate is not an atomic runtime-wide snapshot.