When adding jobs with different priorities to a queue, there is currently no way to extract queue size grouped by priority from the metrics exposed by this service.
Our use-case is that we would have high-prio user-initiated builds and low-prio bot-initiated builds (e.g. dependency bump review builds) in the same queue. Having a large number of low-prio jobs enqueued is fine, but having even a medium-sized number of human jobs enqueued would impact UX, and therefore we'd like to alert on it.
It would be great if you can add a new metric that splits up queue size by priority (which is added as a label).
When adding jobs with different priorities to a queue, there is currently no way to extract queue size grouped by priority from the metrics exposed by this service.
Our use-case is that we would have high-prio user-initiated builds and low-prio bot-initiated builds (e.g. dependency bump review builds) in the same queue. Having a large number of low-prio jobs enqueued is fine, but having even a medium-sized number of human jobs enqueued would impact UX, and therefore we'd like to alert on it.
It would be great if you can add a new metric that splits up queue size by priority (which is added as a label).