studio/ansible
1
0
Fork 0
Code Issues 5 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

Backup failure notifications #2

New Issue
Open
opened 2026-07-12 23:52:56 +02:00 by alessandrovitali · 0 comments
alessandrovitali commented 2026-07-12 23:52:56 +02:00
Owner
Copy Link
Copy Source

Add a simple HTTP ping to the end of the restic backup script and configure uptime kuma / healthcheck service to expect this signal every 24h

curl -fsS -m 10 --retry 5 https://status.uptime.kuma/status-uuid

Add a simple HTTP ping to the end of the restic backup script and configure uptime kuma / healthcheck service to expect this signal every 24h `curl -fsS -m 10 --retry 5 https://status.uptime.kuma/status-uuid`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
bug
Something is not working
 docker
duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 move
question
More information is needed
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
alessandrovitali
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: studio/ansible#2