Add Runner wait times to self-monitoring

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Runner wait times for a shared fleet are an important metric to know if you're trying to figure out if you have enough runners provisioned to meet the demands of your users in your instance. There are some different ways you can get at this information today, but none are easy or integrated with self-monitoring.

Intended users

Further details

https://gitlab.com/gitlab-org/gitlab-ce/issues/67096 captures many more metrics and is related to this topic, but we don't require all of those to get started.

Other issues related to figuring out Runner shared fleet performance on gitlab.com may provide some context for the kind of information needed:

• https://dashboards.gitlab.com/d/000000159/ci?orgId=1&refresh=5m
• https://dashboards.gitlab.com/d/000000159/ci?orgId=1&refresh=5m&fullscreen&panelId=89
• https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/7814
• gitlab-com/www-gitlab-com#5341 (closed)

Proposal

• MVC: start presenting metrics to users that are available today from Prometheus quickly in the self monitoring dashboard.

Archived proposal (not-doing)

• Add wait time as a metric to Prometheus and ship a Grafana chart. If the the Instance Administration project (https://gitlab.com/groups/gitlab-org/-/epics/23670) is open by the time we implement this, we could create a customized "CI Dashboard" in that project.

Permissions and Security

This should only be available to instance administrators.

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

• Current Runner Monitoring Docs
• Additional context from product scaling agenda at https://docs.google.com/document/d/1nMJzrDfG7C14WP5v7P226oPFuXkwqIk7bdIT8ai0DNU/edit?ts=5d84fb07&skip_itp2_check=true&pli=1#bookmark=id.acbz08dge98p

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.