Egest: how Servatum reports to you

Servatum sends each job's status to wherever you already look: signed webhooks, PRTG, Zabbix or Prometheus, and a proof page your customers can open.

Outgoing webhooks

Every run and every status change can be sent as JSON to your own URL. Requests are signed with HMAC-SHA256 in the X-Servatum-Signature header so you can verify they came from Servatum.

{
  "event": "job.status_changed",
  "job": "nightly-full",
  "tier": "offsite-a",
  "from": "ok",
  "to": "missing",
  "last_success_at": "2026-10-23T00:37:12Z",
  "incident_id": "inc_01J..."
}

PRTG, Zabbix, Prometheus

PRTG: an HTTP Data Advanced sensor polls one Servatum URL per job, which returns PRTG-format JSON: status, hours since last good run, size and restore points per tier, with warning and error limits pre-set from your schedule. Pushing to an HTTP Push Data Advanced sensor is also possible if your probe is reachable. Details: PRTG integration.

Zabbix: import the Servatum template. One HTTP agent item fetches status, low-level discovery creates items for every job and tier, and triggers for failed, late and under-retained tiers come pre-defined, plus a nodata() watchdog. Push via trapper or history.push is also possible. Details: Zabbix integration.

Prometheus and Grafana: each account exposes a metrics endpoint you can scrape, with ready-made alert rules for failed, late and under-retained tiers. Details: Prometheus integration.

servatum_tier_status{backup_job="nightly-full",tier="local"} 1
servatum_tier_last_success_timestamp_seconds{backup_job="nightly-full",tier="local"} 1792800000
servatum_tier_last_size_bytes{backup_job="nightly-full",tier="local"} 48211993600
servatum_tier_restore_points{backup_job="nightly-full",tier="offsite-a"} 34

Uptime Kuma and Healthchecks.io: Servatum calls your push or ping URL after each good run, so silence shows up in the tool you already watch.

Proof page and JSON

A proof page shows each tier's status, last known good backup, retention depth, restore-test age and a 90-day incident history. Point a CNAME such as proof.yourdomain.com at Servatum to host it on your own domain.

The same data is available as /proof.json and as an embeddable badge.