Guides
How to collect runner metrics
You cannot tell whether a job is CPU-bound, memory-bound or disk-bound.
5 min read
You cannot tell whether a job is CPU-bound, memory-bound or disk-bound.
Why it happens
GitHub-hosted runners do not expose per-job resource metrics.
How to fix it
- Use a provider that records CPU, memory and I/O per job automatically
- Otherwise run a background sampler and upload the result as an artifact
- Correlate utilization with duration to find right-sizing opportunities
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to track build duration percentilesAverage build time looks fine but developers still complain.How to export CI traces with OpenTelemetryCI timing data lives in a separate tool from the rest of your observability.How to query CI data programmaticallyYou need CI data in a dashboard or a weekly report.How to run a weekly CI health reportCI degrades gradually and nobody notices until it is bad.