Skip to content

docs(merge-queue): add mq_pr_time_in_queue_1h_seconds to Prometheus metrics reference#531

Draft
samgutentag wants to merge 1 commit intomainfrom
sam-gutentag/prometheus-total-time-in-queue
Draft

docs(merge-queue): add mq_pr_time_in_queue_1h_seconds to Prometheus metrics reference#531
samgutentag wants to merge 1 commit intomainfrom
sam-gutentag/prometheus-total-time-in-queue

Conversation

@samgutentag
Copy link
Copy Markdown
Member

Summary

Adds the new mq_pr_time_in_queue_1h_seconds histogram metric to the Prometheus metrics reference table. This metric measures total end-to-end time a PR spends in the queue (entry to exit), covering all phases — not just wait time or test time individually.

Source

Files changed

  • merge-queue/administration/metrics.md — added one row to the rolling 1-hour window metrics table

Open questions

  • Confirm the exact metric name (mq_pr_time_in_queue_1h_seconds) matches what's emitted in production
  • Should we add an example PromQL query for this metric in the "Duration analysis" section?

Test plan

  • Preview in GitBook change request
  • Verify metric name against trunk2 PR diff (trunk-io/trunk2#3439)
  • Check for broken links

…theus docs

Documents the new total time in queue histogram metric, which measures
end-to-end queue duration from entry to exit across all phases. Useful
for teams using batching, bisection testing, or pending failure modes
where wait+test time alone understates total latency.

Pairs with trunk-io/trunk2#3439.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@trunk-staging-io
Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant