Add task/waiting/time metric#18735
Merged
jtuglu1 merged 2 commits intoNov 11, 2025
Merged
Conversation
kfaraz
approved these changes
Nov 11, 2025
riovic918data
pushed a commit
to riovic918data/druid
that referenced
this pull request
Jun 12, 2026
Adds a metric `task/waiting/time` that measures the time it takes for a task to be placed onto the task runner for scheduling+running. This time encompasses initial persistent storage insertion, lock acquisition time, any task queue-related latencies, noisy-neighbor-related slowness, and any other delays between when a task is first added and when it is scheduled for running on the task runner. Useful for debugging issues related to task startup.
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.
Description
Adds a metric
task/waiting/timewhich measures the time it takes for a task to be placed onto the task runner for scheduling+running. This time encompasses initial persistent storage insertion, lock acquisition time, any task queue-related latencies, noisy-neighbor-related slowness, and any other delays between when a task is first added and when it is scheduled for running on the task runner. Useful for debugging issues related to task startup.task/run/time~=task/waiting/time+task/pending/time+ <task run time> .This codepath is called in a hot-loop but emission is non-blocking so this should be alright. Manual testing indicates no material increase in overhead.
Release note
Add task/waiting/time metric.
This PR has: