GiteraGitera Docs

Runners & fleet

Monitor GitHub-hosted and self-hosted runner fleets — status, groups, OS distribution, and queue bottlenecks.

Open in Gitera

/runners shows the health and capacity of the fleet that executes your jobs.

What you see

  • Fleet distribution — GitHub-hosted vs self-hosted counts, OS platforms (Linux, Windows, macOS), and architectures (x64, arm64).
  • Runner groups & status — Active, Idle, and Offline badges, runner labels, and which repositories each group serves.
  • Queue bottleneck metrics — average wait time before a queued job gets picked up, and the groups causing the delays.

If your organization has no self-hosted runners, the self-hosted sections simply show an empty state — that is normal, not an error.

When to look here

  • Queued jobs piling up on the dashboard → find the saturated group.
  • A sudden jump in Linux minutes on the cost page → check whether jobs migrated off self-hosted runners.
  • Planning arm64 or larger-runner purchases → compare utilization first.

Deployment environments

Track deployments to production, staging, QA, and dev across repositories — with approval gates and environment timelines.

Log search

Instant substring search across every indexed CI/CD log line in the organization — with facet filters and saved presets.

On this page

What you seeWhen to look here