PlqnK
/
borgmatic
forked from borgmatic-collective/borgmatic
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Add note about error logs only flowing to Healthchecks for the "create" action.

This commit is contained in:
Dan Helfman 2019-11-17 19:10:11 -08:00
parent 2cc743cf47
commit 78ff734e6c
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/how-to/monitor-your-backups.md
View File

@ -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. 10-kilobyte limit for the logs in each ping.
If an error occurs during the backup, borgmatic notifies Healthchecks after 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 Note that borgmatic sends logs to Healthchecks by applying the maximum of any
other borgmatic verbosity level (`--verbosity`, `--syslog-verbosity`, etc.), other borgmatic verbosity level (`--verbosity`, `--syslog-verbosity`, etc.),