Show what Duplicati's warnings said, and let a job alert on them
The first twenty warning messages of each run are kept with the run and shown on the job and in its history. A job can be set to raise a warning-level alert when its last run finished with warnings (off by default; a muted job raises nothing; maintenance on the machine's server silences it). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
d78aba8bf9
commit
64961b1141
14 files changed
+9241
-24
No files matched your search
+4
-3
@@ -244,14 +244,15 @@ Duplicati tells this app how each backup went ([INTEGRATIONS.md](../INTEGRATIONS
|
||||
| State | Meaning | Alert |
|
||||
|---|---|---|
|
||||
| **In order** | The last run worked and it is not overdue | — |
|
||||
| **Warnings** | The last run finished with warnings (a locked file, say). It still counts as a backup | none |
|
||||
| **Warnings** | The last run finished with warnings (a locked file, say). It still counts as a backup. The page shows **what the warnings said** (open *N warnings* on the job, or on a run in its history) | none — unless the job is set to **alert on warnings** (below): then a warning |
|
||||
| **Failed** | The last run ended in `Error` or `Fatal` | warning; **critical from the second failure in a row** |
|
||||
| **Overdue** | It has not succeeded for longer than it is **expected** to — 2 days unless you set it per job (6 hours to 90 days) | warning; **critical at three times that** |
|
||||
|
||||
The alert says which job, on which machine, why (the first error Duplicati reported) and when the last good backup was. Only the *Backup* operation counts: a compact, a repair or a verification does not say whether the data is safe. A job can be **muted** (no alert; it is still listed),
|
||||
and one that no longer exists can be **forgotten** (with its history; if Duplicati reports it again it is learned again). Each machine can be tied to a server, so **maintenance on that server silences its backups' alerts**.
|
||||
**Alert on warnings** (an operator's button on each job, off until switched on — some jobs always have a few, and a backup with warnings is still a backup) raises a warning-level alert while the job's last run had warnings, naming the job, how many there were and the first thing they said; the next clean run ends it. A job that is muted raises nothing, this included. Maintenance on the server silences it like the others.
|
||||
A job can also be muted, and one that no longer exists can be **forgotten** (with its history; if Duplicati reports it again it is learned again). Each machine can be tied to a server, so **maintenance on that server silences its backups' alerts**.
|
||||
|
||||
What is kept: the last result of each job, and each report for 400 days or 400 reports. `/metrics` has `homelab_duplicati_backup_ok`, `homelab_duplicati_last_success_age_seconds` and `homelab_duplicati_source_size_bytes` for each job. A job is only learned from its first report, so a job that has
|
||||
What is kept: the last result of each job and what its warnings said (up to the first twenty, each cut at 500 characters — Duplicati itself may send fewer than it counted, and the page says so), and each report, with what its warnings said, for 400 days or 400 reports. `/metrics` has `homelab_duplicati_backup_ok`, `homelab_duplicati_last_success_age_seconds` and `homelab_duplicati_source_size_bytes` for each job. A job is only learned from its first report, so a job that has
|
||||
*never* reported is not known to be missing; and because the reports are pushed, **the app being down when a backup finishes** loses that report (the backup shows as overdue only once it is).
|
||||
|
||||
## Nextcloud
|
||||
|
||||
Reference in new issue
Block a user