GitHub Actions monitoring
GitHub Actions monitoring: stop the tab juggling
Workflow runs, DORA metrics, and flaky tests across every repo in one live view. Two-minute setup. No agents. Works alongside GitLab CI, Jenkins, and the rest of your toolchain.
Repos · sorted by last run · last 30 days
Works across every major CI/CD provider
Workflow runs · DORA · Flaky tests
Beyond the Actions tab
Three capabilities every CI/CD Watch tenant uses, each wired specifically into how GitHub Actions reports data. Same JSON sources GitHub uses, lifted into views the Actions tab does not offer.
Workflow runs, every repo, one feed
The Actions tab works for one repo. Twenty repos break it.
Every workflow run across every repo in your org, in one live feed. Filter by status, repo, pipeline, branch, trigger, or time. Drill straight back into the GitHub run page when you need the raw logs.
- Live via efficient API polling: stays under the 5,000 req/hr Actions ceiling using conditional requests
- Filter by status, repo, pipeline, branch, trigger, time window
- Each row links straight to github.com/<org>/<repo>/actions/runs/<id>
Outcome: one tab replaces fifty, without breaking how engineers debug today.
What's needed: OAuth. Nothing in your workflows changes.
Workflow runs across 23 repos
DORA, calculated from Actions runs
Five DORA metrics, from your real workflow run history.
DORA metrics calculated from real workflow run data, including 2024's Rework Rate. Deployments auto-detect on main and master out of the box. Configure named rules in five minutes for reusable workflows or deploys that live on non-default branches.
- Deploy Frequency, Lead Time, Change Failure Rate, MTTR, and Rework Rate per repo
- Auto-detected from main / master, with deployment-classification accounting for matrices and composite actions
- Trend over 7 / 30 / 90 days, per-repo or aggregated, with period-over-period regression alerts
Outcome: DORA defensible to leadership, without manual reporting.
What's needed: OAuth. Auto-detection covers the simple cases.
DORA by repo · 30 days · ranked by deploy frequency
Flaky tests, surfaced and tracked
Upload JUnit XML once. We surface every test that flips across branches.
GitHub Actions writes test output to your workflow as files. Upload the JUnit XML as an artifact with actions/upload-artifact and we parse it on the way in. Each test gets a flip rate, failure rate, and current status so the most disruptive ones surface first.
One line of YAML if you don't already
- uses: actions/upload-artifact@v4
with:
name: junit
path: '**/junit.xml'- Per-test flip rate scored across branches over a rolling 30-day window
- Failure rate and current status per test, sortable in the table
- Matrix-test results merged per logical test, not duplicated per matrix leg
Outcome: fix the disruptive tests first, with real flip-rate data to triage them.
What's needed: JUnit XML uploaded as an artifact. Most teams already do this.
Flaky tests, last 30 days, sorted by flip rate
Same connect, more depth
How we work with GitHub Actions
Three more capabilities the same connect unlocks. None of them are GitHub-Actions-only, but each pays off particularly well on Actions estates where YAML config, runner-type variance, and trunk-vs-flow branching all swing the numbers.
Cost
Cost-optimization opportunities ranked by potential saving
Right-sizing recommendations, redundant-step detection, and waste categorisation. Each opportunity shows what to change and the annualised saving for taking the action.
Audit
Audit rules catch CI/CD hygiene gaps across the estate
21 built-in rules check for missing lint, no unit tests, absent SAST, secrets-in-config patterns, and more. Findings ranked by severity; each one names the repo and the fix.
Strategy
Branching strategy auto-detected per repo
Trunk-based, GitFlow, GitHub-flow detected from your real branch and merge patterns. DORA metrics get a per-strategy lens so trunk-based repos aren't penalised for not having long-lived release branches.
All from one connect
Plus the rest of the toolkit
The three capabilities above are what you'll use most. Same connect also gives you cost tracking, PR health, stability classification, performance ratings, security insights, Slack, CLI, and an MCP server. No extra integrations.
Cost tracking →
Compute charges plus developer wait time. Waste auto-categorised by type. Team tier.
PR health →
Per-repo CI failure rates, reviewer wait time, and PR-to-deploy latency. Team tier.
Stability classification →
Every pipeline auto-classified healthy, flaky, or broken. Trend detection on each.
Performance ratings →
Per-pipeline performance scoring across the estate. Spot the slow outliers.
Security insights →
Per-repo security-scan detection rolled up across the estate. Business tier.
Slack notifications →
Pipeline failures, regressions, and degradation alerts in your team channel. Team tier.
CLI →
Query pipeline status, costs, and DORA from your terminal. Pipe it anywhere.
MCP server →
Hook Claude, Cursor, or any AI agent into live pipeline state.
Pricing
Flat per tenant
Start free for one team. Team and Business tiers are flat monthly rates per tenant. Enterprise is custom for organisations needing SSO, audit logging, and security review.
Free
For one team getting started with up to 3 repos.
- 3 repos
- 1 team member
- Workflow runs, DORA, flaky tests
- Cost view (last 30 days)
- Email support
Team
Flat rate per tenant. Up to 20 repos and 10 team members.
- 20 repos
- 10 team members
- Everything in Free
- Cost tracking with full history
- PR health, performance ratings
- Slack notifications, CLI, MCP server
Business
Flat rate per tenant. Up to 100 repos and 50 team members.
- 100 repos
- 50 team members
- Everything in Team
- Audit findings and cost-optimization opportunities
- Priority support
Comparison
How CI/CD Watch compares
A 10-person team running GitHub Actions across ~20 repos. Headline pricing only; deeper feature comparisons live on the linked pages.
CI/CD Watch$29 / mo flat (Team) | ||||
|---|---|---|---|---|
| Workflow run monitoring | Live cross-repo feed | Yes | Limited | Yes |
| DORA metrics from CI data | All five, auto-detected | Add-on | Yes | No |
| Cost tracking (compute + wait time) | Yes, with wait time | Compute only | Wait time only | No |
| Flaky test surfacing | Flip-rate and failure-rate | Test count | No | Yes |
| Pricing model | Flat per tenant | Per committer + spans | Per contributor | Flat tiers |
| Setup time | ~2 min OAuth | Agent install per repo | OAuth + config | ~5 min |
Competitor pricing reflects each vendor's published headline rate. See the linked comparison pages for fuller feature matrices and verified sources.
~2 min
to connect via OAuth
0
agents to install in your runners
5
DORA metrics from day one
Flat
per-tenant pricing
FAQ
GitHub Actions specifics
- How is this different from GitHub's own insights and the Actions tab?
- GitHub's native views are per-repo. Workflow runs, billing, insights, all scoped to one repository. CI/CD Watch is the cross-repo lens: one feed across every repo, DORA aggregated across them, flaky tests sortable across the estate. It complements the Actions tab; we link back to it on every row.
- Will it slow down our Actions or affect billing?
- No. CI/CD Watch reads from GitHub's API after runs complete. It does not modify your workflows, install runners, or trigger billable activity. The polling is rate-limit-aware and stays comfortably under the 5,000 req/hr ceiling using conditional requests.
- How does CI/CD Watch get our workflow data?
- Via the standard GitHub REST API using the OAuth scopes you grant at connect time (read-only on workflow runs and repository metadata). No webhooks, no GitHub App install beyond the OAuth flow, no agents in your runners.
- What if our workflows use reusable workflows for deploys?
- The deployment-classification model accounts for reusable workflows, matrix builds, and composite actions when counting deploys for DORA. Auto-detection covers the common cases; more involved attribution (e.g. crediting deploys back to a calling repo when deploy logic lives elsewhere) is on the roadmap.
- What about self-hosted runners?
- Fully supported. Self-hosted runs appear in the workflow-runs feed and feed DORA the same as hosted runs. If you've configured a cost rate for your self-hosted infrastructure under Settings, cost calculations apply that rate; otherwise self-hosted minutes are tracked but not costed.
- How long does setup take?
- Around two minutes. OAuth to GitHub, pick which repos to include, and the first workflow-run feed populates within minutes.
- Is pricing tied to workflow runs or seats?
- Neither. CI/CD Watch is flat per tenant: $0 Free, $29 Team, $99 Business per month. Repo and team-member caps differ per tier; consumption inside those caps is unmetered.
- Can we get DORA metrics across GitHub Actions and Jenkins or GitLab?
- Yes. Connect each provider separately; DORA metrics include runs from every connection. Useful for mixed estates mid-migration where part of the team has moved to Actions and part is still on Jenkins.
- How do you handle GitHub Enterprise Server?
- Supported on the Business tier. Outbound HTTPS from your GHES instance to api.cicd.watch, OAuth via your GHES instance. No inbound connections required.
More on CI/CD monitoring
Read, compare, or get started
Guide
Audit
How CI/CD Watch audits your pipelines for missing tests, missing lint, and other CI/CD hygiene gaps.
Guide
Deployment detection
Auto-detection covers main and master. Configure named rules for reusable workflows or non-default branches.
Blog
GitHub Actions dashboard
What a multi-repo GitHub Actions dashboard needs to do, and the patterns that actually move the numbers.
Blog
Flaky tests: what they are, why they happen, how to fix them
Practical patterns for catching flaky tests early, ranking them by impact, and clearing them without halting feature work.
Blog
The true cost of CI/CD: compute, wait time, and waste
Compute is half the bill. Developer wait time is usually the bigger half. The taxonomy of CI/CD cost and where the waste lives.
Blog
What are DORA metrics and why should you track them?
The four (now five) signals from DORA Research that measure how well a software team delivers. What each one means and how to read them.
One tab replaces fifty.
Connect GitHub Actions in two minutes. Workflow runs, DORA, and flaky tests across every repo, plus the cost view free for 30 days.