Integration · CI / CD
GitHub Actions
Workflow durations, failure rate, queue time.
What gets collected
A webhook plus GraphQL polling. Metrics: workflow_run duration, success rate, queue time per runner pool.
Requirements
- ✓GitHub App with workflow:read
- ✓webhook on workflow_run
- ✓runner_pool labels
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
gha.workflow.durationgha.success.rategha.queue.timegha.runner.utilizationSetup steps
- 1Create a GitHub App with workflow:read
- 2Webhook on check_run / workflow_run
- 3runner_pool labels
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
GitHub Actions
Frequently asked questions
- What does Unimoni collect from GitHub Actions?
- Workflow durations, failure rate, queue time. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across GitHub Actions and everything else in one place.
- How long does it take to connect GitHub Actions?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the GitHub Actions integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is GitHub Actions monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.