Guides
How to query CI data programmatically
You need CI data in a dashboard or a weekly report.
4 min read
You need CI data in a dashboard or a weekly report.
Why it happens
Clicking through the Actions UI does not scale and cannot show trends.
How to fix it
- Use the provider's metrics API for durations, cost and cache statistics
- Fall back to the GitHub Actions REST API for run and job metadata
- Schedule a workflow that writes the report to a channel with a named owner
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 collect runner metricsYou cannot tell whether a job is CPU-bound, memory-bound or disk-bound.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 run a weekly CI health reportCI degrades gradually and nobody notices until it is bad.