GitDash
DocsAPI playgroundGitHub
Open GitDash
GitDash Docsv4.7.1
GitHub API playground
  • Introduction
  • Quick start
  • Deployment
  • Configuration
  • Auth modes
  • Access control
  • Caching & rate limits
  • Security model
  • Data sources
  • Feature overview
  • Repositories
  • Repository · Overview
  • Repository · Workflows
  • Repository · Pull requests
  • Repository · Team
  • Repository · Issues
  • Repository · Security
  • Repository · Audit trail
  • Workflow detail
  • Alerts
  • Team insights
  • Contributor & 1:1 prep
  • Cost
  • Reports
  • Org overview & health
  • Settings
  • AI insights
  • Metrics Reference
  • DORA 4 Keys
  • PR Cycle Time
  • PR Lifecycle Health
  • Workflow Overview
  • Performance Tab
  • Reliability Tab
  • Team & People
  • CI & Alert Metrics
  • API Reference
  • FAQ & Troubleshooting
  • Contributing
  • Release Notes
  • Data & privacy
GitHub RepositoryReport an Issue
GitDash Docs

CI & Alert Metrics

CI-based DORA (Workflow DORA Tab)

The Workflow Detail page has a dedicated DORA tab that computes the 4 Keys from CI run data rather than from PRs and GitHub Releases. This gives a workflow-level proxy view of delivery performance.
MetricCI-based calculationDifference from repo-level DORA
Deploy FrequencyCompleted runs (any result) per day over the span of the runs loaded for this workflow (50 by default). No branch filter.Repo-level uses Releases or merged PRs. CI-based counts every successful workflow run — useful for workflows that deploy on every merge.
Lead TimeMedian time from a run being created to it completing (queue wait plus execution); p95 alongside.Repo-level measures first commit → PR merged. CI-based measures only the CI run itself — no coding or review time.
Change Failure RatePercentage of completed runs whose conclusion is failure (timed-out, cancelled and skipped runs are not failures but stay in the denominator).Repo-level uses hotfix/revert PR heuristics. CI-based is a direct CI failure rate — more precise but only reflects build failures, not production incidents.
MTTRAverage time from a failed run to the next successful run on the same branch.Repo-level uses hotfix PR cycle time. CI-based measures build recovery time — does not account for manual intervention or rollbacks.

The DORA tab also shows a DORA Performance Levels reference table with the industry benchmarks from the State of DevOps Report for all four metrics.

Alert Metrics

Alert rules in the Alerts page use these metrics. Each rule fires when the metric crosses the configured threshold within the evaluation window.

MetricCategoryFires when…
Failure RateCI% of failed runs in the window exceeds threshold
Duration P95CI95th-percentile run duration (minutes) exceeds threshold
Queue Wait P95CI95th-percentile queue wait (minutes) exceeds threshold
Success StreakCIConsecutive failures without a success exceeds threshold
PR Throughput DropPeopleMerged PRs this week dropped by more than N% vs the prior week
Review Response P90PeopleP90 time-to-first-review exceeds N hours
After-Hours Commits %People% of commits outside the organization's workday exceeds threshold
PR Abandon RatePeople% of PRs closed without merge exceeds threshold
Unreviewed PR AgePeopleAny open PR has been waiting for a first review for more than N business days
PreviousTeam & PeopleNextAPI Reference

GitDash v4.7.1 — GitHub Actions Dashboard

Open source on GitHubData & privacyReport an issue