
If we don't have a POST_COMMANDS_INCOMPLETE then POST_COMMANDS_FAILURE will trigger. This may be a bit misleading as we are doing backups of live systems and it is almost expected that a file will change or disappear during backup. Instead, we report backup as "up" with a message that the backup was incomplete.
3 lines
205 B
Django/Jinja
3 lines
205 B
Django/Jinja
#!/bin/sh
|
|
{# We can't signal other statuses than up or down I think, but we can attach a descriptive message #}
|
|
curl --silent '{{ restic_secrets.uptime_kuma_url }}?status=up&msg=Incomplete%20backup&ping='
|