-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
Open
Labels
bugSomething isn't workingSomething isn't working
Description
π I have found these related issues/pull requests
N/A
π‘οΈ Security Policy
- I have read and agree to Uptime Kuma's Security Policy.
π Description
I've setup a basic monitor of a docker container. I've also setup a notification monitor to call a webhook when monitors go up/down.
The webhook is being called when the monitor goes down, but it's not being called when it goes back up.
Looking at my docker logs for UK, it seems that it detects the container as being down/exited. It then detects it as pending, but it never goes back to "up".
U.K. does now show that the autoheal container is Up, but there's nothing in the log, and no webhook triggered.
Any ideas?
π Reproduction steps
See above
π Expected behavior
Webhook should be called when container goes back Up.
π Actual Behavior
Webhook only being called when Container goes Down.
π» Uptime-Kuma Version
Version: 2.0.0-beta.3
π» Operating System and Arch
Docker on Ubuntu
π Browser
Edge
π₯οΈ Deployment Environment
Version: 2.0.0-beta.3
Frontend Version: 2.0.0-beta.3
π Relevant log output
2025-07-31T16:38:03+01:00 [MONITOR] WARN: Monitor #2 'autoheal': Failing: Container State is exited | Interval: 20 seconds | Type: docker | Down Count: 0 | Resend Interval: 0
2025-07-31T16:38:23+01:00 [MONITOR] WARN: Monitor #2 'autoheal': Pending: starting | Max retries: 0 | Retry: 0 | Retry Interval: 30 seconds | Type: docker
2025-07-31T16:38:53+01:00 [MONITOR] WARN: Monitor #2 'autoheal': Pending: starting | Max retries: 0 | Retry: 0 | Retry Interval: 30 seconds | Type: docker
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working