[docker] container w/ healthcheck comes up -> no event or notication #2945

New issue

Open

opened 2026-02-28 03:12:33 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 03:12:33 -05:00

Owner

Originally created by @daberlin on GitHub (Dec 20, 2023).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

Hi
When a docker container goes down, an event is logged and a notification is sent.
As soon as it comes up again, both event and notification are only sent if NO health check exists. Containers with a health check get yellow first and then green - not neother event nor notification are created.

👟 Reproduction steps

Configure monitor for container with and without health check. Stop both and restart.

👀 Expected behavior

Both containers issue an event and a notification when going down and another one when coming up again.

😓 Actual Behavior

Both containers issue an event and a notification when going down. Only the container w/o a health check sends a notification when coming up again.

🐻 Uptime-Kuma Version

1.23.10

💻 Operating System and Arch

Linux / Docker

🌐 Browser

not relevant, but Firefox

🐋 Docker Version

24.0.7

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @daberlin on GitHub (Dec 20, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description Hi When a docker container goes down, an event is logged and a notification is sent. As soon as it comes up again, both event and notification are only sent if NO health check exists. Containers with a health check get yellow first and then green - not neother event nor notification are created. ### 👟 Reproduction steps Configure monitor for container with and without health check. Stop both and restart. ### 👀 Expected behavior Both containers issue an event and a notification when going down and another one when coming up again. ### 😓 Actual Behavior Both containers issue an event and a notification when going down. Only the container w/o a health check sends a notification when coming up again. ### 🐻 Uptime-Kuma Version 1.23.10 ### 💻 Operating System and Arch Linux / Docker ### 🌐 Browser not relevant, but Firefox ### 🐋 Docker Version 24.0.7 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman added the

bug

A:monitor

labels

2026-02-28 03:12:33 -05:00

deekerman commented

2026-02-28 03:12:35 -05:00

Author

Owner

@sauloaguiar93 commented on GitHub (Dec 22, 2023):

Hello, good morning.

I experienced a similar situation but resolved it by performing a backup, stopping the container. Then, I removed the SQLite files from the volume, recreated the container, and restored the data. As a result, everything started working again without issues.

@sauloaguiar93 commented on GitHub (Dec 22, 2023): Hello, good morning. I experienced a similar situation but resolved it by performing a backup, stopping the container. Then, I removed the SQLite files from the volume, recreated the container, and restored the data. As a result, everything started working again without issues.