Drift Detection
Drift Detection helps you ensure that your live infrastructure matches what you declared in code. Axio continuously compares the actual deployed state with the desired state defined in your workflow.
Infrastructure can change outside of your workflows — manual updates, emergency fixes, or external tools. Drift detection identifies these differences so you can fix them early and keep environments reliable.
How it works
Axio compares your desired state with the actual state using your configured IaC engine.
(Terraform, OpenTofu, Pulumi)
in your cloud
the two states
Drift Detection Dashboard
The Drift Detection page provides two views for monitoring infrastructure drift.
Watched
The Watched tab shows workspaces and stacks that are currently being monitored for drift.
| Field | Description |
|---|---|
| Stack | Name of the stack being monitored |
| Workspace | Workspace containing the stack |
| Engine | IaC engine used by the stack, such as Terraform |
| Level | Scope at which drift detection is configured |
| Status | Result of the latest drift check |
| Last checked | Time when the stack was last checked |
| Schedule | Frequency at which the stack is checked |
| Actions | Available actions for the watched stack |
All Sources
The All Sources tab shows the available infrastructure sources that can be selected for drift monitoring.
Watch a Stack
Use Watch stack to add a stack to Drift Detection.
Once a stack is being watched, Axio periodically runs a drift check according to its configured schedule.
A watched stack appears in the Watched tab with its current status and last check time.
Add a stack to Drift Detection to automatically check it according to the configured schedule.
Drift Check Status
Each watched stack displays the result of its most recent check.
The latest drift check completed successfully and the infrastructure is consistent with the declared configuration.
A drift check failed or could not complete successfully.
When checks fail, open the affected workspace and run a new check.
Troubleshooting Failed Checks
If a drift check shows Check failed:
- Open the affected workspace.
- Review the stack configuration.
- Check whether the IaC plan or preview can complete successfully.
- Verify that the assigned runner is available and has the required IaC engine.
- Run a new drift check.
- Review the updated status.
A failed drift check does not necessarily mean that infrastructure has drifted. The check itself may have failed because the IaC plan or preview could not complete.