Monitoring
CI/CD monitoring
inline watches your GitHub Actions runs. A failure gets a root-cause comment on the pull request that caused it, and flaky tests and builds that have crept slower than their baseline collect on the CI alerts page.
Turning monitoring on and choosing which signals it watches are admin tasks. Everyone else meets it as a comment on their own pull request.
#The three signals
CI/CD monitoring
Failed GitHub Actions runs get a root-cause comment on the PR. Flaky tests and builds that creep slower than their baseline surface here before they cost your team time.
Success rate (14d)
94%
Failed runs (14d)
11
Open alerts
3
Triage spend
$•.••
Open by signal
Recent alerts
Every CI alert is one of three kinds, and the badge on the row says which.
| Kind | What it means |
|---|---|
| Failure | A run failed. inline reads the logs, works out why, and comments the cause on the pull request. |
| Flaky | A run failed and then passed on a re-run without the code changing, which is the signature of a test that cannot be trusted. |
| Slow run | A workflow is taking noticeably longer than its own baseline, so a build that has gradually got slower shows up before anyone times it. |
Open by signal counts the three, which is the quickest way to see whether your team is dealing with real breakage or with flakiness.
#Reading a CI alert
CI alerts is the full list. Each row shows the kind, the severity, the workflow it came from, the repository and the pull request, with a link out to the run on GitHub.
For a failure, the useful part has usually already arrived: the root-cause comment is on the pull request, so the person who broke the build reads it without opening the portal.
#The totals
Four totals sit across the top: Success rate (14d), Failed runs (14d), Open alerts and Triage spend. The first two are the pair to watch over time, and Open alerts is what is waiting now.
#Choosing what it watches
The Actions Settings tab has one switch per signal. Enable CI monitoring is the master switch, and AI failure triage, Flaky test detection and Build duration tracking turn the three signals on and off independently. Email alerts decides whether they also arrive by email.
Monitor new repositories by default decides what happens when someone connects a repository, and each repository in the list can be switched on or off by hand, with an optional branch filter.
CI/CD monitoring is included with Pro. See Plans and billing.