Backup result monitoring

Bring scheduled backup reports into the same workspace as uptime, SSL, alerts, and status pages. Use JSON or email 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 client backup succeeds but with warning details your team should inspect.
• A recurring check needs an audit trail for latest success and failure.

What is included

Create backup sources with ingest tokens, receive JSON or email reports, and inspect the latest result state from the portal.

Tokenized sources

Issue one ingest token per backup source and rotate or revoke it from the portal.

JSON reports

Post status, message, duration, and finished-at metadata from backup tooling.

Email reports

Use source-specific ingest addresses for systems that send backup emails.

Stale detection

Set stale-after windows so missing reports become visible.

Ingest examples

Use these shapes to connect backup tooling that can send JSON reports or structured email notifications.

1) Post a successful database backup

Post a successful backup run with duration and completion time.

checks:
  - source: nightly-database
    status: success
    message: Backup completed
    duration_seconds: 418
    finished_at: 2026-06-16T01:10:00Z

Example payload

2) Record a failed fileshare backup

Post a failed backup run with the operator-facing message.

checks:
  - source: client-fileshare
    status: failure
    message: Snapshot destination is unavailable
    finished_at: 2026-06-16T02:05:00Z

Example payload

3) Capture a warning state

Normalize warning states from tools that report partial completion.

checks:
  - source: exchange-archive
    status: warning
    message: Completed with skipped mailbox
    details:
      skipped: 1

Example payload

4) Ingest an email report

Use email ingest when a backup product cannot post JSON directly.

checks:
  - to: [email protected]
    subject: Backup Success - Client NAS
    body: Job completed in 12 minutes

Example payload

Who it could help

MSPs & agencies

Centralize backup success, failure, and stale-report visibility per client workspace.

Operations teams

Track recurring jobs without logging into every backup vendor portal.

Compliance workflows

Keep a recent operational record for backup checks and incident review.

Need backup monitoring?

Share the backup systems you operate and the report format you want to ingest.

Back to solutions →