You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
If scheduled backups fail silently in the background, users might not notice (for instance, they're not looking into the log files) and are without backups for days or weeks.
Describe the solution you'd like
Every OS these days has support for notifications and it would be great if backrest would add support for that. The feature list mentions notification support for third-party services like Discord or Slack, but a local notification would be useful as well, esp. as default value for a new configuration.
Notifications could be sent when a backup finishes, fails or misses a variable amount of runs.
Additional context
I'm currently using custom scripts to create those notifications on Linux and Windows but that is not a viable solution to a lot of users.
The text was updated successfully, but these errors were encountered:
I agree that native support is a good idea, this is fairly low priority for me as scripts are a solid workaround -- but it is the most common scripting use case from what I see in discussions. Current projects on my plate are multihost synchronization and improving the form system, but I've tagged it as a good first issue as it's pretty approachable.
Yes, scripting gets the basics done (notification per executed backup job).
Looking at how backup notifications are done on Windows 10 or on macOS, I think those solutions are, however, more reliable than scripts. For instance, backups might start only if the computer is on power supply or if it can reach a specific host or network. Now, should those conditions never be met for instance for two weeks or a month, Windows and macOS will create a notification to make users aware about this. Another example is a monthly backup job I scheduled using resticprofile including notifications on errors, but that job didn't execute for months so none of my notification scripts got actually triggered.
On both cases, you'd be receive a warning on Windows and macOS.
Is your feature request related to a problem? Please describe.
If scheduled backups fail silently in the background, users might not notice (for instance, they're not looking into the log files) and are without backups for days or weeks.
Describe the solution you'd like
Every OS these days has support for notifications and it would be great if backrest would add support for that. The feature list mentions notification support for third-party services like Discord or Slack, but a local notification would be useful as well, esp. as default value for a new configuration.
Notifications could be sent when a backup finishes, fails or misses a variable amount of runs.
Additional context
I'm currently using custom scripts to create those notifications on Linux and Windows but that is not a viable solution to a lot of users.
The text was updated successfully, but these errors were encountered: