Skip to content
  • Server Operations

Rolling patch and reboot across a fleet

Monthly patching is coordinated by hand, takes a full maintenance window of attention, and stalls when one host misbehaves.

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

    Resolve the target set and preview it before starting

  2. 2

    Drain each host, patch, reboot and wait for health

  3. 3

    Verify before moving to the next wave

  4. 4

    Stop the run automatically when a wave fails

What the run verifies

A patched fleet with a per-host result and a run that halts on trouble instead of propagating it.

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

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.