qbit_manage: alert when a run fails or stops happening #385
Labels
No labels
audit-work
bug
docs
general-admin
major-upgrade
needs-vps-sync
new-service
on-hold
outside-work
post-podman
renovate
upstream
vps
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
mysticalsoap/docker#385
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
qbit_manage ran into its qBittorrent version ceiling on 2026-10-02 and exited with
CRITICALon every scheduled run for six days before anyone noticed (PR #383). The config'swebhooks.erroris empty, so a run that dies before its first command is indistinguishable from a quiet one, and nothing in Prometheus watches it either (the container staysUp, the scheduler loop never exits).webhooks.errorandrun_endaccept any HTTP endpoint; ntfy's publish URL works with the same token pattern ascrowdsec_ntfy_token/ntfy_alertmanager_access_token(secret file,!ENVin config.yml).qbit_manage_last_success_timestamp) written byrun_end, with a Prometheus rule when it goes stale past a schedule interval, which also catches a hung run.