# GitHub Actions Runner Exporter

GitHub Actions Runner Exporter is a self-hosted development app. Prometheus exporter for GitHub Actions self-hosted runner status (online/busy), plus repo CI health, PR counts and Dependabot alerts, polled from the org API on a rate-limit-friendly cache. It is open source and self-hosted, installable on Unraid.

Canonical page: https://ourlocalhost.com/app/2849/github-actions-runner-exporter

## Description

Prometheus exporter for GitHub Actions self-hosted runner status (online/busy), plus repo CI health, PR counts and Dependabot alerts, polled from the org API on a rate-limit-friendly cache.

## Platform availability

Available on 1 of 10 platforms: Unraid.

## Health score

51/100 (Fair), based on 3 of 4 factors.
- Maintained: 84 (last commit 7 days ago)
- Popular: 10 (2 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)

## Links

- Unraid: https://ca.unraid.net/apps/github-actions-runner-exporter-1m3rty90v34ccd?q=github-actions-runner-exporter

## Common questions

### Does the exporter use different cache intervals for runner status and repo stats?

Yes. Runner status uses RUNNER_CACHE_TTL, default 15s, and org/repo stats use ORG_CACHE_TTL, default 5m.

### How is CI status measured?

CI status is tracked per active workflow, not per repository. This stops a failing workflow from being hidden by a later unrelated successful run.

### How does the exporter report GitHub rate limits?

It exposes the remaining core API budget for the scarcest active window and also each active window with its reset time. GitHub counts per region, so one token can have several windows at once.

### What does a 0 on github_runners_up or github_org_up mean?

It means a stale cache is being served or the first poll is still running. For org/repo stats, the first poll can take about a minute after startup at ~25 repos.

---
Source: Our Local Host (https://ourlocalhost.com/app/2849/github-actions-runner-exporter), the self-hosted and open-source app directory.
