GitHub Actions Runner Exporter
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…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
51/100 Fair
- Maintained
- 84last commit 7 days ago
- Popular
- 102 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 22 days ago
- GitHub stars
- 2
- Open issues
- 0
- Last commit
- 2026-11-14
- Latest release
- v1.6.1
- License
- MIT
- Activity
- declining
Checked 7 days ago - source: GitHub (drumandbytes/github-actions-runner-exporter)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set runner scope and location first Before starting, set RUNNER_SCOPE and the matching location setting, such as REPO_URL, ORG_NAME, or ENTERPRISE_NAME. Without the right scope and location, the runner cannot ask GitHub where to register, so startup will fail. source
- Choose one login method for GitHub Provide either GitHub App details, a personal access token (a long secret that signs you in), or a pre-made RUNNER_TOKEN. The container needs one of these to register the runner; if it is missing or wrong, the runner cannot start accepting jobs. source
- Keep runner config and work folder safe The runner saves its connection details in /actions-runner and can load persistent settings from CONFIGURED_ACTIONS_RUNNER_FILES_DIR. Keep that folder and your mounted work directory safe, because deleting them can break registration or lose files used by jobs. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
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.
Answers sourced from github.com
Community
- GitHub action exporter for monitoring with prometheus and grafana (forum)
- Error "Waiting for a runner to pick up this job" using GitHub Actions (forum)
Collected 48 days ago - public community threads