Cross-Repo Dashboard for Infrastructure Operations
Erik Osterman
CEO & Founder of Cloud Posse
|
Erik Osterman
CEO & Founder of Cloud Posse
Erik is the founder of Cloud Posse and creator of Atmos. With over a decade of experience helping teams adopt Terraform at scale, he is passionate about open-source infrastructure tooling and developer experience.
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.
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.
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.
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.
|