Duplicati: flag warnings run after run, and forecast how much room backups take
A job whose last three runs in a row all finished with warnings is flagged and raises an alert (on by default, switchable off per job). The size of the destination, and its quota where the storage says, are read from the reports and kept with each run; the Stored column shows the growth and, where the room is known, when it will be full, with an alert inside the disk-forecast window. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
333146e8e3
commit
4f077d4f4a
15 files changed
+10115
-14
No files matched your search
@@ -170,6 +170,8 @@ That works on every Duplicati version, needs no login handshake and leaves nothi
|
||||
- **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.
|
||||
- **Why a machine has no jobs.** "Last heard" only says something arrived on the address. Each machine's card on the page also says **what the last report was** — a backup (with the job and how it ended), another operation that was set aside (compact, repair, test … only a *Backup* makes a job), or one that **could not be read** with the reason (no `ParsedResult`, not valid JSON …) — and how many of each have come since the machine was added. Administrators can open **What was sent** to see the first 600 characters of an unreadable report, to see its form; others see the reason but not the text. A machine with no job yet and only set-aside reports is told to check `--send-http-level=All`.
|
||||
- **Warnings in a row.** One run with warnings is common; the page and an alert say when the **last three runs in a row** all finished with warnings (*Warnings 4 runs in a row*; alert key `duplicati-streak:<job>`). It is on for every job and a button turns it off for one that always has a few (*Stop streak alerts*); it is not raised for a job that already alerts on every warning run, nor for one that has failed or is overdue (their own alerts say that).
|
||||
- **How much room the backups take.** Duplicati says how big the backups are where they are kept (`BackendStatistics.KnownFileSize`) and, for some kinds of storage, how much room there is (`TotalQuotaSpace`). Both are read (the plain-text form too) and the size is kept with every run. The *Stored* column on the page shows it with the growth over the last 180 days — *+3.4 GB a month*, *not growing*, *size goes up and down* — only once there are five readings over a week, and nothing is claimed from less. Where the room is known it also says *full in about N days*, and when that is within the **disk forecast window** (Settings → Alerts, 14 days by default; 0 switches it off) and the growth is steady (a straight line fits at least 0.8) it is an alert (`duplicati-growth:<job>`; critical at three days or less). A storage that does not say how much room it has is never forecast to fill: the growth is shown, nothing more. Compacting makes the size drop now and then, which lowers the fit and keeps a jagged size from raising a false alarm.
|
||||
- What it does with them — alerts, `/metrics`, the history — is in [MONITORING.md](docs/MONITORING.md#duplicati-backups).
|
||||
|
||||
### Proxmox Backup Server
|
||||
|
||||
Reference in new issue
Block a user