Notifications only when there are issues, and daily/weekly/monthly backup scheduling using the daemon

[tis24dev]

Hi! Based on your requests, I’ve developed a notification filter. If you enable health checks, you can set your preferred notification level: always receive notifications, receive notifications only for warnings, or receive notifications only for failures. Health checks are important for preventing missed issues that wouldn’t trigger a notification (such as a case with no problems).
I’m also working on the ability to use your PBS and Borg systems as backup destinations to simplify management and maintenance for you!

[RLSinRFV]

@tis24dev
I can't seem to find this notification filter.

I'd only like to receive notifications when there is a warning, not a successful backup with no warnings. I currently have HEALTHCHECK_ENABLED=true, and have these other settings:
NOTIFY_ON=warning
TELEGRAM_ENABLED=false
EMAIL_ENABLED=false
GOTIFY_ENABLED=false
WEBHOOK_ENABLED=false

I'm curios about the two settings below as I do use GOTIFY (I had the GOTIFY_ENABLED =true and GOTIFY_PRIORITY_SUCCESS=0 but still received notifications on successful, no-warning backups).

HEALTHCHECK_NOTIFY_GOTIFY_URL=
HEALTHCHECK_NOTIFY_GOTIFY_ID=

I have my GOTIFY server on the URL line and the GOTIFY key on the ID line, but am NOT receiving messages. What am I missing?

[tis24dev]

@RLSinRFV Gotify has not changed: configure it exactly as before, with GOTIFY_ENABLED=true, GOTIFY_SERVER_URL and GOTIFY_TOKEN.

HEALTHCHECK_NOTIFY_GOTIFY_URL and HEALTHCHECK_NOTIFY_GOTIFY_ID configure healthchecks, not Gotify. They point to a check on your own healthchecks server, in self mode only, that watches whether Gotify delivered. Leave them empty: in self mode, any HEALTHCHECK_NOTIFY_* variable that is set keeps every run notified, whatever NOTIFY_ON says.

We are improving the documentation of these variables, because their comments were easy to misread.