🔎✨Introducing Drift Cause: Adding Context to Drift Management

We’re excited to announce Drift Cause, bringing visibility and accountability to managing infrastructure drift.

When detecting a drift, have you ever wondered what caused it, who made the change, and why? Drift Cause helps answer these questions by providing detailed information about who was responsible when it occurred, and how it was triggered—whether through a CLI command, a manual UI update, or another action.

By linking codified infrastructure with out-of-code audit logs, Drift Cause gives teams the context they need to efficiently investigate, resolve, and prevent future drifts.

Drift Cause connects codified infrastructure with real-world changes, offering a clear view of the user responsible for a change, the method used (e.g., UI, CLI, API), and the exact time the change occurred.

You can also drill down into event metadata, such as IP addresses or JSON logs, directly in the cloud provider’s console.

To learn more about how to use Drift Cause, visit here.