Runbooks

Where runbooks come from

Open Automation → Runbooks. The page is what your team has learned to fix. There are two sources:

• •Learned. When a finding is resolved through Resolve with AI, Opservo takes the commands from that thread that succeeded, prefers the ones that changed something over read-only checks, and saves up to 12 of them as a runbook titled after the finding. The same class of problem on any server groups under one runbook; numbers in the title (sizes, counts) are ignored when grouping.
• •Written by hand. Click + New runbook, give it a title such as "Disk full on /var", and add steps one command per line. Tick the box on each step that changes something on the server.

Each card shows how often the fix has worked and where: for example Fixed 3× · web-01, web-02 · last 12 Sep. Steps that write to the server carry a writes badge.

Recurring right now

If a runbook’s problem is open on a server at this moment, the card is highlighted and says open now on that server. Those runbooks sort to the top of the page, followed by the most battle-tested.

Editing and deleting

Click Edit on any card to change the title or steps. For a learned runbook your edited version wins from then on, even as new resolutions are recorded. Delete removes a hand-written runbook; for a learned one it hides it so it is not rebuilt from history.

Running a runbook

Click ▶ Run on servers… on a card. This opens the fleet-run composer with the runbook selected; its steps become the run’s steps, in order. Pick one server or many, choose a rollout, and confirm. On each server the steps run one after another and stop at the first non-zero exit. The results page shows each step’s output per server.

Running a runbook needs the owner or admin role, a server with remote actions on, and the Growth plan or higher, exactly like any other command. Every step is signed and recorded in that server’s command history.