浏览代码

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

Dan Helfman 5 年之前
父节点
当前提交
78ff734e6c
共有 1 个文件被更改,包括 3 次插入1 次删除
  1. 3 1
      docs/how-to/monitor-your-backups.md

+ 3 - 1
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.
 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.),