Duplicati: know when a backup failed or has gone quiet
Duplicati reports each operation to a secret address (its own send-http-url option), so nothing calls Duplicati and no password for it is kept. Each machine is a source; each job is learned by name and shows its last result, duration, size, changes and a history. A failed run is a warning (critical from the second in a row); one that has not succeeded for longer than expected (per job, 2 days by default) is a warning, critical at three times that. Maintenance on the machine's server silences them; /metrics series added. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
12f2662465
commit
2f082ca5c2
23 files changed
+8047
-4
No files matched your search
@@ -116,6 +116,28 @@ the dashboard views themselves load fine. (UniFi, Nginx Proxy Manager, Home Assi
|
||||
- Verified against the Uptime Kuma 1.23 and 2.0 source and against a stand-in server speaking the same
|
||||
protocol; not yet run against a live Uptime Kuma.
|
||||
|
||||
### Duplicati
|
||||
|
||||
Duplicati is different from the other integrations: **this app never calls Duplicati**, and no password for it is kept. Duplicati can tell a URL how each operation went (its own `send-http-url` option), so each machine running it is a *source* with a secret address, and its reports come in.
|
||||
That works on every Duplicati version, needs no login handshake and leaves nothing to leak from this side.
|
||||
|
||||
- **Set up** (Backups → Duplicati → *Add a machine*, administrators): give the machine a name and, if you like, the server it runs on. You are shown, **once**, an address of the form `https://<this app>/api/duplicati-report/hlm_d_…` and the three options to add in Duplicati under
|
||||
**Settings → Default options → Advanced options** (so every job on that machine reports):
|
||||
|
||||
```
|
||||
--send-http-url=https://<this app>/api/duplicati-report/hlm_d_…
|
||||
--send-http-result-output-format=Json
|
||||
--send-http-level=All
|
||||
```
|
||||
|
||||
`send-http-level=All` matters: by default Duplicati only reports problems, and a backup that quietly stops reporting could not be told from one that works. The plain-text format is also read, but JSON carries the name of the job and the figures reliably.
|
||||
For one job only, add the same options to that job's advanced options instead.
|
||||
- **What is read** from each report: the operation (only *Backup* counts — a compact, repair or test is set aside), the result (`Success`, `Warning`, `Error`, `Fatal`), the job's name, when it began and ended, the duration, the size of what was examined, the files added, changed and deleted, the number of
|
||||
warnings and errors and the first message. A job is learned from its first report, by name; the same name on another machine is another job.
|
||||
- **The address is the access.** It is a long random token (stored only as a SHA-256 hash, shown once); all it allows is to say how a backup went. It answers a wrong token with "not found", limits requests per address, and takes POST or PUT. Removing the machine ends it.
|
||||
- **Not verified against every Duplicati version** — the report fields are read defensively from Duplicati's published output (the results at the top or under `Data`, the job's name among `Extra`). A report the app cannot read is answered "OK (not a report this app can read)" and the page does not learn from it.
|
||||
- What it does with them — alerts, `/metrics`, the history — is in [MONITORING.md](docs/MONITORING.md#duplicati-backups).
|
||||
|
||||
### Proxmox Backup Server
|
||||
|
||||
- **Config fields:** Proxmox Backup Server URL, API token ID, API token secret, allow self-signed certificate
|
||||
|
||||
Reference in new issue
Block a user