Skip to content
  • Workflow Orchestration
  • Server Operations

Configuration drift detection and ticketing

Configuration diverges from baseline over time, and the divergence is discovered during an audit or an incident.

The workflow

How StackHeal handles it

Each step is a registered action, a condition or an approval. Nothing here is a general-purpose command.

  1. 1

    Query configuration state across the estate on a schedule

  2. 2

    Compare against the expected baseline

  3. 3

    Record deviations with asset detail

  4. 4

    Open tickets for anything out of policy

What the run verifies

Drift surfaced continuously as actionable tickets rather than discovered under pressure.

Where a person stays involved

Any step that changes state can be configured to require an approval, and a run that cannot verify its own outcome escalates rather than closing. The confidence threshold, the blast-radius limit and the approver are all yours to set.

Related products

StackHeal products share one workflow engine, one action catalogue and one run history.

Learn more about Server Operations

Server Operations

Run recurring server and facility tasks the same way every time, with a record of each run.

Learn more
Learn more about Workflow Orchestration

Workflow Orchestration

Connect systems and automate repetitive operational processes.

Learn more

See this workflow built against your systems.

We will walk through the intake, the policy checks, the approval points and the verification step using your own tooling.