Backup result monitoring
Bring scheduled backup reports into the same workspace as uptime, SSL, alerts, and status pages. Use tokenized JSON ingest to see failures, stale jobs, and latest successful runs.
Why it matters
Many operational failures happen outside public websites. Backup jobs can fail overnight, succeed only partially, or stop reporting entirely until someone checks manually.
- • A backup job reports failed status after a storage or permission issue.
- • A nightly report never arrives and the source becomes stale.
- • A backup reports an unexpected state that your team should inspect.
- • A recurring check needs an audit trail for latest success and failure.
What is included
Starter and Scale can create tokenized backup sources, receive JSON reports, and inspect the latest result state from the portal. Inbound email ingest is not available at launch.
Issue one ingest token per backup source and rotate or revoke it from the portal.
Post status plus optional externalId, summary, occurredAt, and payload fields.
Use the JSON token endpoint; inbound email ingest is unavailable at launch.
Set stale-after windows so missing reports become visible.
Ingest examples
Create one source per backup job and POST one JSON object to its token endpoint. The occurredAt value is Unix time in milliseconds.
Post a successful backup run with duration and completion time.
{
"externalId": "nightly-database-2026-07-19",
"status": "success",
"summary": "Backup completed in 418 seconds",
"occurredAt": 1784423400000,
"payload": { "durationSeconds": 418 }
}Post a failed backup run with the operator-facing message.
{
"externalId": "client-fileshare-2026-07-19",
"status": "failure",
"summary": "Snapshot destination is unavailable",
"occurredAt": 1784426700000,
"payload": { "destination": "secondary-storage" }
}Values outside the success and failure families are stored as Unknown for review.
{
"externalId": "exchange-archive-2026-07-19",
"status": "warning",
"summary": "Completed with one skipped mailbox",
"payload": { "skippedMailboxes": 1 }
}Who it could help
Centralize backup success, failure, and stale-report visibility per client workspace.
Track recurring jobs without logging into every backup vendor portal.
Keep a recent operational record for backup checks and incident review.
Share the backup systems you operate and the report format you want to ingest.