Varqeni Help

Set up on-call

Updated 11 November 2026

On-call lives in one file on the Varqeni host, /etc/opsagent/oncall.yaml, owned by root so that Varqeni itself cannot change it. Fortis sets it up 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

  • List each person with their name, their Fortis sign-in name (login) and their email for Teams mentions.
  • Set the rota order, the handoff day and time, and the time zone. The primary changes at each handoff; the next person is the secondary.
  • Set the escalation steps, for example the primary at once, the secondary after 10 minutes, everyone after 20.
  • Set how long to wait for the autopilot on a fault it owns (hold_for_autopilot_min) and which causes are low urgency.
  • Choose the paging tools (teams, pagerduty) and list the approvers. Keys stay secrets on the host.
  • Check the file with opsagent oncall-check, which prints who is on call now, then set enabled: true.

What you should see: The On-call view shows the rota and rules as Varqeni reads them. With enabled: false it records who it would have paged and tells nobody.

What it can and cannot do

Can

  • Set the rota, handoffs, escalation, autopilot hold, low-urgency causes, paging tools and approvers in one checked file.

Cannot

  • Be changed by Varqeni itself, or page anyone while it is disabled or invalid.

If it does not work

  • A mistake in the file is shown in the On-call view, and nobody is paged until it is fixed.

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