Log Duplicati verifier transport errors

master
Carlo Costanzo 4 weeks ago
parent e0684f9773
commit d3623e2f2d

@ -10,6 +10,7 @@
# Notes: Home dashboard consumes `infra_*` entities for exceptions-only alerts.
# Notes: Domain warning threshold is <30 days; critical threshold is <14 days.
# Notes: Nightly Duplicati verification runs at 08:00 after the 05:30 Duplicati job and docker_14 reboot window.
# Notes: Duplicati transport/API errors are logged only; repairs are reserved for proven failed or stale backups.
# Notes: Monthly HA log hygiene review requests Telegram + GitHub issue follow-up only; Joanna must wait for approval before any changes.
# Notes: Numeric WAN telemetry exposes state_class so recorder can keep long-term statistics.
# Notes: Docker host root disk usage uses Glances-backed normalized sensors; raw Glances sensors are recorder/logbook-filtered.
@ -605,6 +606,7 @@ automation:
verify_backup_name: "{{ verify_detail.get('backupName', 'Docker_Configs') }}"
verify_latest_result: "{{ verify_detail.get('latestResult', {}) if verify_detail is mapping else {} }}"
verify_last_success: "{{ verify_detail.get('lastSuccessfulRun', {}) if verify_detail is mapping else {} }}"
verify_transport_issue: "{{ verify_status in ['api_error', 'unknown'] }}"
- choose:
- conditions: "{{ verify_healthy }}"
sequence:
@ -616,6 +618,15 @@ automation:
continue_on_error: true
data:
issue_id: user_infra_duplicati_backup_failure
- conditions: "{{ verify_transport_issue }}"
sequence:
- service: script.send_to_logbook
data:
topic: "BACKUP"
message: >-
Duplicati verifier could not prove backup health because the verification service returned
status {{ verify_status }} with issue {{ verify_issue }}. No repair card was opened because
this is verifier transport state, not a confirmed backup failure.
default:
- service: repairs.create
data:

Loading…
Cancel
Save

Powered by TurnKey Linux.