Guides
How to run a weekly CI health report
CI degrades gradually and nobody notices until it is bad.
4 min read
CI degrades gradually and nobody notices until it is bad.
Why it happens
There is no regular review, so slow drift never triggers action.
How to fix it
- Report p95 duration, cache hit rate, flake rate and spend weekly
- Show the trend, not just the current value
- Give the report an owner — an unowned dashboard changes nothing
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 query CI data programmaticallyYou need CI data in a dashboard or a weekly report.