Varqeni Help

Run an incident: declare, severity, command, updates and action items

Updated 11 November 2026

Varqeni opens most incidents itself. People still run them. Everything here is a request Varqeni checks against the on-call rota and keeps with the incident, so it appears in the timeline, the write-up and the incident story.

AvailabilityAvailable to everyone with early access to Varqeni.

Steps

  • Declare an incident: in On-call, choose Declare an incident, say in a few words what is wrong, pick the system and a severity. Varqeni collects and seals the system's evidence as it would for its own incident and pages the person on call. You lead it unless you hand it over. From the host: opsagent declare --title "Checkout hangs" --sev 2 --by "Emma Clarke".
  • Severity: SEV1 critical, people are affected now; SEV2 major, a core service is failing; SEV3 minor, degraded or at risk; SEV4 low, no one affected yet. Varqeni sets one from the cause and how sure it is; change it in the incident panel, with a reason if you like. Your paging tool gets the same severity.
  • Commander: choose Take command, or hand it to someone else on the rota.
  • Status updates: write where it stands and choose Post update. It goes to the incident's thread in Teams (and Slack, when connected) and stays with the incident.
  • Action items: what to do afterwards, with an owner, a due date and a link to the follow-up. Tick one when it is done. They are listed in the write-up.

What you should see: The incident panel shows the severity, the commander, the latest updates and the action items under the response buttons.

What it can and cannot do

Can

  • Declare an incident, set its severity, take or hand over command, post status updates to the incident's thread and keep action items, each checked against the rota and kept with the incident.

Cannot

  • Let anyone off the on-call rota change any of it, or post updates to people outside your team. A status page is built and not switched on.

If it does not work

  • Not on the on-call rota: only people on the rota can declare or change these. Ask your administrator.
  • Not done: someone is not on the on-call rota: command can only go to someone on the rota.

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