Varqeni Help

PagerDuty

Updated 11 November 2026

See Paging and escalation for when Varqeni pages.

AvailabilityAvailable to everyone with early access to Varqeni.

How it works

  • Setup: a PagerDuty service with an Events API v2 integration. Your administrator adds its integration key, which is kept as a secret on the host.
  • One fault, one incident: every notice about the same incident goes to the same PagerDuty incident, however long the fault lasts.
  • Acknowledge: acknowledging, approving or declining in the console or on the Teams card sends an acknowledgement to PagerDuty. Built and tested against recorded requests; its live test against PagerDuty is pending.
  • Resolve: when the system recovers, the PagerDuty incident resolves.
  • Escalation inside PagerDuty follows its own policy once it has the incident.
  • What it cannot do yet: show an acknowledgement made inside PagerDuty back in Varqeni.

What it can and cannot do

Can

  • Open one PagerDuty incident per fault and resolve it when the system recovers.

Cannot

  • Show an acknowledgement made inside PagerDuty back in Varqeni, or count on acknowledging from Varqeni yet: built, live test pending.

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