Varqeni Help

Custom operations: write a runbook

Updated 11 November 2026

Runbooks are short files on the Varqeni host, in /etc/opsagent/runbooks/, owned by root so Varqeni cannot change them. Fortis writes them with you during early access.

AvailabilityFor the person who runs Varqeni for your team. In early access that is usually Fortis, working with you.

Steps

  • When: the cause (for example disk_filling), the targets it applies to (patterns such as runner:* or servicelab/*) and the lowest confidence it accepts, medium or high.
  • Do: one fix that Varqeni itself recommends for that cause and can run on that system. Anything else is refused when the file is read.
  • Mode approve (the default): the page says the runbook recommends the fix, and an approver runs it from the console.
  • Mode auto: Varqeni runs the fix at once, checks it worked, and pages a person only if it did not. This needs the runbook's own passed fault trial, keeps to a limit per hour, and stops for the kill switch and maintenance.
  • Several steps: instead of one fix, a runbook can list steps: wait a while, check the system is still failing (if it recovered on its own, nothing runs), run a fix, and check it stays healthy for a set time. A person is paged if any step fails. Up to eight steps and 30 minutes of waiting and checking.
  • Shared: one runbook can name several systems of the same kind, such as two change data capture pipelines. Each incident is judged on its own system.
  • Check the file with opsagent runbooks --dry-run: it lists the runbooks and replays each against your past incidents, on every system it is shared with.

What you should see: The Policies view lists each runbook with its trigger, fix, mode and trial, and can dry-run it against past incidents.

What it can and cannot do

Can

  • Turn a cause into a known fix, or several steps with checks between them, approved each time or, after its own trials, run on its own within limits.
  • Share one runbook across pipelines or systems of the same kind.
  • Replay a runbook against past incidents before it is trusted.

Cannot

  • Name a fix Varqeni does not recommend for that cause, mix systems of different kinds in one runbook, or wait and check for more than 30 minutes.

If it does not work

  • A file with a mistake is listed in red in the Policies view and never runs.

Still stuck? Contact support or email info@fortisdatagroup.com.