One Dashboard for All Your Repos
Managing infrastructure across dozens of repositories shouldn't mean dozens of tabs. The new cross-repo dashboard aggregates deployment metrics and operational events into a single view — so you can see what's happening everywhere, at a glance.
Workflow Runs
3,891
+8%
3,612 completed · 279 failed
1,247 detections · 89 remediations
Instance Health
94%
Healthy
847 in sync · 42 drifted · 12 error
Across all repositories
Merge Time
4.2h
-12%
47 PRs merged this period
Avg time from open to merge
Change Failure Rate
3.2%
-8%
279 failed of 3,891 runs
Across all repositories
Built-In DORA Metrics
DORA (DevOps Research and Assessment), popularized by the Google Cloud SRE handbook, identified four key metrics that predict software delivery performance: deployment frequency, lead time for changes, change failure rate, and time to restore service. Teams that consistently track and improve these metrics ship faster with fewer failures.
These metrics apply just as much to infrastructure-as-code as they do to application code. Slow merge times signal review bottlenecks or overly complex changes. A rising change failure rate means your Terraform changes are breaking in production — and you're finding out too late.
The cross-repo dashboard now surfaces merge time (a proxy for change velocity) and change failure rate directly alongside your operational metrics, so you can track delivery health without leaving the dashboard.
Real-Time Event Feed
Every workflow execution, drift detection, and deployment across your entire workspace flows into one unified event feed. Filter by repository, status, or time range to zero in on what matters.
Latest Events
Show:
| Event | Ref | Type | Time |
|---|---|---|---|
PR #342 opened | feat/add-rds-module · a1b2c3d | PR | 7m ago |
Drift detection | main · e4f5g6h | Drift | 16m ago |
PR #341 synchronize | fix/vpc-cidr-range · b2c3d4e | PR | 32m ago |
Release v2.4.1 published | main · c3d4e5f | Release | 51m ago |
PR #340 closed | chore/upgrade-provider · d4e5f6g | PR | 1h ago |
Page 1 of 3 (12 total events)
Why This Matters
Teams running Atmos at scale often have 20+ repositories with hundreds of stacks. Before this, you'd need to check each repo individually. Now, one dashboard tells you if anything needs attention — and links you straight to the source.
