# Adding queue wait time to buildkite-agent-metrics **URL:** \ **Category:** Features Requests\ **Created:** [September 3, 2026, 10:39pm UTC](https://forum.buildkite.community/t/adding-queue-wait-time-to-buildkite-agent-metrics/4626 "2026-09-03T22:39:37Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jlisee-glydways](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/jlisee-glydways/32/1719_2.png) [@jlisee-glydways](https://forum.buildkite.community/u/jlisee-glydways)\ **Post date:** [September 3, 2026, 10:39pm UTC](https://forum.buildkite.community/t/adding-queue-wait-time-to-buildkite-agent-metrics/4626/1 "2026-09-03T22:39:37Z")
I would like to signal boost this `buildkite-agent-metrics` feature request: [Wait time of the oldest scheduled job as a metric](https://github.com/buildkite/buildkite-agent-metrics/issues/92) Since it was posted 7 years ago the underlying APIs at Buildkite now have this information ([see post](https://forum.buildkite.community/t/queue-wait-times-metric/1220/9)) but it would be much better if every customer didn’t have to do this and the metrics collector just provided it directly. It’s also an awkward patch to propose to `buildkite-agent-metrics` because the service has a nice clean signal token and API endpoint which does _not_ have this information, so it would need to learn to talk to another API, I think this is best done internally by buildkite. ---
**Author:** ![lizette](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/lizette/32/1161_2.png) [@lizette](https://forum.buildkite.community/u/lizette)\ **Post date:** [September 4, 2026, 12:29am UTC](https://forum.buildkite.community/t/adding-queue-wait-time-to-buildkite-agent-metrics/4626/2 "2026-09-04T00:29:45Z")
> [@jlisee-glydways](#): > > [see post](https://forum.buildkite.community/t/queue-wait-times-metric/1220/9) Hi @jlisee-glydways , Welcome to the Buildkite Support Community! 👋 Thanks for reaching out here and for re-raising this issue on the `buildkite-agent-metrics`. Good news is we’ve already assessed the work required to support this. However, it is still in the backlog and could not commit on a delivery timeline. However, I can report. back to our engineering team on your interest. You will reply back here - [Feature request: Wait time of the oldest scheduled job as a metric · Issue #92 · buildkite/buildkite-agent-metrics · GitHub](https://github.com/buildkite/buildkite-agent-metrics/issues/92) - when we have updates on this work. Cheers! ---
**Author:** ![jlisee-glydways](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/jlisee-glydways/32/1719_2.png) [@jlisee-glydways](https://forum.buildkite.community/u/jlisee-glydways)\ **Post date:** [September 4, 2026, 3:23pm UTC](https://forum.buildkite.community/t/adding-queue-wait-time-to-buildkite-agent-metrics/4626/3 "2026-09-04T15:23:20Z")
Lizette thanks for the quick response, I look forward to an update from engineering on the issue. This might seem minor but it’s actually really high impact work. It provides a clear signal that helps teams catch bad build cluster situations early and fix them before large impact to their company. This work prevents each customer building this themselves, probably after a few painful incidents, and this assumes they actually know they need this. With AI/LLM use surging investing in features that let your customers handle extreme load CI is a key competitive advantage over competitors like GitHub Actions and their very poor reliability. ---
**Author:** ![Micheal](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/micheal/32/1588_2.png) [@Micheal](https://forum.buildkite.community/u/Micheal)\ **Post date:** [September 4, 2026, 3:29pm UTC](https://forum.buildkite.community/t/adding-queue-wait-time-to-buildkite-agent-metrics/4626/4 "2026-09-04T15:29:59Z")
Hi @jlisee-glydways thanks for the additional context here, I will follow up on the assessment with these points for further review as I also understand your points here