Dashboard Metrics
The Infrastructure Overview dashboard shows metrics computed from the dependency graph and state metadata. This page explains what each metric means, how it is calculated, and what to look for.
Control Plane Status
These four cards reflect the operational state of your Terraform transactions.
Active Transactions
Number of Terraform transactions currently in progress against this state. An active transaction means a terraform plan or terraform apply is running. A count of zero means the system is idle.
Last Transaction
The outcome of the most recent completed transaction:
| Status | Meaning |
|---|---|
| Committed | The transaction was applied successfully. |
| Aborted | The transaction was manually cancelled before completion. |
| Failed | The transaction encountered an error during apply. |
The relative time shown below indicates how recently the transaction completed.
Recent Changes
A summary of transaction activity over a rolling time window (typically the last 24 hours). Shows the count of committed, aborted, and failed transactions. Use this to gauge how actively the state is being modified and whether failures are occurring.
Last Change Impact
The blast radius of the most recent committed transaction — the number of resources that were directly or transitively affected by the change. A high number indicates a wide-reaching modification; zero means no recent changes.
State Structure
These four cards summarize the shape and size of your Terraform state.
Resources
Total number of resource instances tracked in the current Terraform state. Each instance maps to one real infrastructure object (e.g., an S3 bucket, an IAM role).
Modules
Number of distinct Terraform modules used in this state. Modules group related resources into reusable, composable units. A high count may indicate a well-factored configuration.
Providers
Number of different cloud or service providers (e.g., AWS, GCP, Azure) referenced by resources in this state. Multi-provider states have broader infrastructure scope.
Graph Density
Total dependency edges divided by total resource instances, expressed as edges/resource.
| Value | Interpretation |
|---|---|
| < 1.0 | Sparse — most resources are standalone or have few dependencies. |
| ~1.0 | Each resource has roughly one dependency on average. Common for simple configurations. |
| > 2.0 | Heavily interconnected — changes are more likely to cascade across multiple resources. |
For example, a state with 50 resources and 75 dependency edges has a density of 1.50 edges/res.
Risk & Dependency Analysis
These cards highlight structural risks in the dependency graph.
Largest Dependency Blast Radius
The single resource whose change would affect the most other resources. Stategraph finds this by traversing all transitive dependencies for every resource and selecting the one with the largest reach. Click the card to open a blast radius visualization for that resource.
Top Dependency Hotspot
The resource that the most other resources depend on (highest inbound reference count). A high count means changes to this resource could cascade widely. This is different from blast radius — hotspot counts how many resources point to this one, while blast radius counts how many resources are reachable from a given one.
Graph Structure
- Roots: Resources with no dependencies — the entry points of the dependency graph. These are typically foundational resources (VPCs, projects, resource groups).
- Leaves: Resources that nothing else depends on — the terminal nodes. Leaves are often end-user-facing resources (DNS records, load balancers).
Composition
These panels show how your resources are distributed across types and providers.
Resource Type Distribution
Breakdown of resource instances by Terraform type, ranked by count. The top five types are shown with bar charts. Click a row to view all resources of that type in the inventory. A heavily skewed distribution may indicate repetitive infrastructure (e.g., many security group rules).
Provider Distribution
Breakdown of resource instances by cloud or service provider. Single-provider states show just the provider name. Multi-provider states show a stacked bar chart and percentage breakdown. Click a provider to filter the inventory.
Control Plane Insights
These metrics are computed from the dependency graph and state metadata. They surface information that the Terraform CLI does not show.
Largest Module
The Terraform module containing the most resources. Extremely large modules may benefit from decomposition into smaller, focused units for better maintainability and blast radius isolation.
Most Deployed Module
The module that appears the most times across different resource instances. High reuse indicates a well-designed shared module. Low reuse alongside many modules may suggest duplicated patterns that could be consolidated.
Top Resource Type
The Terraform resource type (e.g., aws_security_group_rule, aws_iam_policy) with the most instances in this state.
Orphaned Candidates
Resources flagged by graph analysis as potentially unused. A resource is considered an orphaned candidate when no other resource depends on it (leaf node) and it is either outside any module or has at most one dependency. Resources inside a module with multiple dependencies are excluded because modules typically bundle related resources intentionally. Not every flagged resource is actually orphaned — review each one to decide whether to remove it or leave it in place.
Provider Distribution (Chart)
A doughnut chart showing the percentage breakdown of resources across providers. The top four providers are shown individually; the rest are grouped as "Other."
Top Resource Types (Chart)
A horizontal bar chart showing the five most common resource types and their instance counts.