Varqeni Help

Silences and maintenance windows

Updated 11 November 2026

A silence covers one system or every system, and can be limited to some causes. While it is on, Varqeni still investigates and records everything, but sends no page and no escalation; the incident's timeline names the silence. When it ends and the fault is still there, the page goes out as usual. A fault that recovers inside the silence closes quietly.

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

Steps

  • Open On-call. Under Silences, choose the system, how long, and why. Only people on the on-call rota can make or end one.
  • For planned work later, set Starting: that makes a maintenance window, shown as coming until it starts.
  • By default the autopilot and automatic runbooks stand back too, so a change you make on purpose is not undone. Tick Let the autopilot and automatic runbooks still fix things if they should keep working.
  • Choose End now to finish early. A silence always has an end, at most 24 hours after it starts.
  • On the Varqeni host the same is opsagent silence add --system <id> --minutes 60 --reason "..." --by <your name>, opsagent silence list and opsagent silence end <id> --by <your name>.

What you should see: Each silence shows who made it, why and until when. The old maintenance file, /etc/opsagent/maintenance, still works and counts as a silence on every system with no end; it is being retired, so use a silence instead.

What it can and cannot do

Can

  • Hold pages and escalations back for one system, some causes or everything, now or as a later maintenance window, and keep the autopilot from undoing work you do on purpose.

Cannot

  • Last more than 24 hours, stop named approvals (use the kill switch), or stop Varqeni investigating and recording.

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