Varqeni Help

Alerts from Prometheus Alertmanager and other monitoring

Updated 11 November 2026

You do not have to move your alerting. Varqeni takes Alertmanager's webhook, or a simple JSON alert from any tool, and treats it like a fault it found itself.

AvailabilityAvailable to everyone with early access to Varqeni.

How it works

  • Route it: give an alert the label varqeni_route with the system it is about, or let your administrator match labels to systems.
  • What happens: Varqeni collects that system's evidence, read-only, and names the cause when its own checks see one. When they see nothing, the alert itself is the incident and the person on call is paged with it as it is.
  • Repeats and recovery: an alert that keeps firing is one incident. When it resolves, the incident is marked recovered and the page resolves. One that keeps firing and resolving is grouped and told once.
  • What it never does: act on an alert by itself. The autopilot works only on what Varqeni found, and any fix still needs a named approval.

What you should see: The alert is part of the sealed record: the report, the timeline and the write-up show it.

What it can and cannot do

Can

  • Open an incident for an alert from Alertmanager or any tool, investigate the system it is about, and resolve the page when the alert resolves.

Cannot

  • Act on an alert by itself, or take an alert that names no system it watches.

If it does not work

  • Nothing arrives: the alert has no route and no default system, so Varqeni dropped it. Add the varqeni_route label.
  • Refused with 401: the sender is not using the intake token. Alertmanager uses it as a bearer token; other tools sign the body.

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