From 78ff734e6cfd594e374d544253a268b454147d15 Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Sun, 17 Nov 2019 19:10:11 -0800 Subject: [PATCH] Add note about error logs only flowing to Healthchecks for the "create" action. --- docs/how-to/monitor-your-backups.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/how-to/monitor-your-backups.md b/docs/how-to/monitor-your-backups.md index baa78e3e6..cddadb010 100644 --- a/docs/how-to/monitor-your-backups.md +++ b/docs/how-to/monitor-your-backups.md @@ -125,7 +125,9 @@ in the Healthchecks UI, although be aware that Healthchecks currently has a 10-kilobyte limit for the logs in each ping. If an error occurs during the backup, borgmatic notifies Healthchecks after -the `on_error` hooks run, also tacking on logs including the error itself. +the `on_error` hooks run, also tacking on logs including the error itself. But +the logs are only included for errors that occur within the borgmatic `create` +action (and not other actions). Note that borgmatic sends logs to Healthchecks by applying the maximum of any other borgmatic verbosity level (`--verbosity`, `--syslog-verbosity`, etc.),