starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Multiple Rocket.chat Notifications Triggering for One site at the same time #4639

New issue

Open

opened 2026-02-28 04:10:11 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-28 04:10:11 -05:00

Owner

Originally created by @nileshA-addweb on GitHub (Jan 26, 2026).

I found some notification-related issues, but none specifically address multiple Rocket.Chat notifications being triggered simultaneously for the same event.

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.

📝 Description

When multiple monitors go down or exceed the interval at the same time, Rocket.Chat receives multiple notifications simultaneously. This results in notification spam instead of a single alert per event.

👟 Reproduction steps

Configured multiple monitors (approx. 40).
Configured Rocket.Chat as the notification channel.
Bring multiple monitored sites down at the same time (or exceed the interval).
Observe that multiple notifications are triggered simultaneously.

👀 Expected behavior

Only one notification should be triggered per alert event, even when multiple monitors fail simultaneously.

😓 Actual Behavior

Multiple notifications are triggered at the same time for the same alert condition, causing spam in Rocket.Chat.

🐻 Uptime-Kuma Version

2.1.0-beta.2-nightly-20260121024714

💻 Operating System and Arch

Ubuntu 22.04.2 LTS | Arch: x86_64

🌐 Browser

Version 143.0.7499.169 (Official Build) (64-bit)

🖥️ Deployment Environment

Runtime Environment

Docker: 29.1.5
Docker Compose: 1.29.2

Database

MariaDB: Embedded (used by Uptime Kuma)

Database Storage

Filesystem: ext4
Storage Medium: SSD

Uptime Kuma Setup

Deployment: Docker
Image: louislam/uptime-kuma:nightly2
Number of monitors: ~40

Host System

OS: Ubuntu 22.04.2 LTS
Architecture: x86_64

📝 Relevant log output

This setup is expected to generate only one alert per event, but currently multiple alerts are sent, leading to notification flooding.

Originally created by @nileshA-addweb on GitHub (Jan 26, 2026). ### 📑 I have found these related issues/pull requests I found some notification-related issues, but none specifically address multiple Rocket.Chat notifications being triggered simultaneously for the same event. ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description When multiple monitors go down or exceed the interval at the same time, Rocket.Chat receives multiple notifications simultaneously. This results in notification spam instead of a single alert per event. ### 👟 Reproduction steps 1. Configured multiple monitors (approx. 40). 2. Configured Rocket.Chat as the notification channel. 3. Bring multiple monitored sites down at the same time (or exceed the interval). 4. Observe that multiple notifications are triggered simultaneously. ### 👀 Expected behavior Only one notification should be triggered per alert event, even when multiple monitors fail simultaneously. <img width="801" height="106" alt="Image" src="https://github.com/user-attachments/assets/b0a0d810-b2e7-4879-a197-f34390710338" /> <img width="1349" height="605" alt="Image" src="https://github.com/user-attachments/assets/bfcb98a6-f5e9-499d-9188-94b2ec800766" /> ### 😓 Actual Behavior Multiple notifications are triggered at the same time for the same alert condition, causing spam in Rocket.Chat. ### 🐻 Uptime-Kuma Version 2.1.0-beta.2-nightly-20260121024714 ### 💻 Operating System and Arch Ubuntu 22.04.2 LTS | Arch: x86_64 ### 🌐 Browser Version 143.0.7499.169 (Official Build) (64-bit) ### 🖥️ Deployment Environment **Runtime Environment** - Docker: 29.1.5 - Docker Compose: 1.29.2 **Database** - MariaDB: Embedded (used by Uptime Kuma) **Database Storage** - Filesystem: ext4 - Storage Medium: SSD **Uptime Kuma Setup** - Deployment: Docker - Image: louislam/uptime-kuma:nightly2 - Number of monitors: ~40 **Host System** - OS: Ubuntu 22.04.2 LTS - Architecture: x86_64 ### 📝 Relevant log output ```bash session This setup is expected to generate only one alert per event, but currently multiple alerts are sent, leading to notification flooding. ```

deekerman added the

bug

cannot-reproduce

labels

2026-02-28 04:10:11 -05:00

deekerman commented

2026-02-28 04:10:14 -05:00

Author

Owner

@louislam commented on GitHub (Jan 26, 2026):

Only one notification should be triggered per alert event, even when multiple monitors fail simultaneously.

Not by our current design, it is expected to send one notification per monitor.

@louislam commented on GitHub (Jan 26, 2026): > Only one notification should be triggered per alert event, even when multiple monitors fail simultaneously. Not by our current design, it is expected to send one notification per monitor.

deekerman commented

2026-02-28 04:10:16 -05:00

Author

Owner

@louislam commented on GitHub (Jan 26, 2026):

Feel free to open feature request instead, thanks for the report.

@louislam commented on GitHub (Jan 26, 2026): Feel free to open feature request instead, thanks for the report.

deekerman commented

2026-02-28 04:10:16 -05:00

Author

Owner

@nileshA-addweb commented on GitHub (Jan 26, 2026):

@louislam There was a typo. Let me explain the issue again (as below).

Description
When single monitor go down or exceed the interval at the same time, Rocket.Chat receives multiple notifications simultaneously. This results in notification spam instead of a single alert per event.

Reproduction steps
-Configured multiple monitors (approx. 40).

Configured Rocket.Chat as the notification channel.
Bring single monitor/site down at the same time (or exceed the interval).
Observe that multiple notifications are triggered simultaneously for this single site/monitor

Expected behavior
Only one Rocket.chat notification should be triggered per alert event.

Actual Behavior
Multiple notifications are triggered at the same time for the same alert condition, causing spam in Rocket.Chat.

@nileshA-addweb commented on GitHub (Jan 26, 2026): @louislam There was a typo. Let me explain the issue again (as below). **Description** When single monitor go down or exceed the interval at the same time, Rocket.Chat receives multiple notifications simultaneously. This results in notification spam instead of a single alert per event. **Reproduction steps** -Configured multiple monitors (approx. 40). - Configured Rocket.Chat as the notification channel. - Bring single monitor/site down at the same time (or exceed the interval). - Observe that multiple notifications are triggered simultaneously for this single site/monitor **Expected behavior** Only one Rocket.chat notification should be triggered per alert event. **Actual Behavior** Multiple notifications are triggered at the same time for the same alert condition, causing spam in Rocket.Chat.

deekerman commented

2026-02-28 04:10:16 -05:00

Author

Owner

@louislam commented on GitHub (Jan 26, 2026):

I checked the history, the logic implementation of rocket-chat almost had not been changed since 2021.

https://github.com/louislam/uptime-kuma/commits/master/server/notification-providers/rocket-chat.js

So it may not be related to rocket.chat. I will check the notification logic later, see if any pull requests cause this.

Btw, you are using an old nightly version, it could be buggy. You should upgrade to 2.1.0-beta.3.

@louislam commented on GitHub (Jan 26, 2026): I checked the history, the logic implementation of rocket-chat almost had not been changed since 2021. https://github.com/louislam/uptime-kuma/commits/master/server/notification-providers/rocket-chat.js So it may not be related to rocket.chat. I will check the notification logic later, see if any pull requests cause this. Btw, you are using an old nightly version, it could be buggy. You should upgrade to 2.1.0-beta.3.

deekerman commented

2026-02-28 04:10:16 -05:00

Author

Owner

@louislam commented on GitHub (Jan 26, 2026):

The notification logic had been modified a bit by #6745 on 2026-01-18. And your nightly version is 20260-01-21.

I have to investigate.

@louislam commented on GitHub (Jan 26, 2026): The notification logic had been modified a bit by #6745 on 2026-01-18. And your nightly version is 20260-01-21. I have to investigate.

deekerman commented

2026-02-28 04:10:16 -05:00

Author

Owner

@nileshA-addweb commented on GitHub (Jan 26, 2026):

Do I try to upgrade to 2.1.0-beta.3 or wait for your updates?

@nileshA-addweb commented on GitHub (Jan 26, 2026): Do I try to upgrade to 2.1.0-beta.3 or wait for your updates?

deekerman commented

2026-02-28 04:10:16 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 26, 2026):

I don't think we recently merged anything that could affect this.
Upgrading is recomended though to prevent already resolved issues affecting you.

Could you make sure that you don't have a few monitors for this?
What are the logs?

@CommanderStorm commented on GitHub (Jan 26, 2026): I don't think we recently merged anything that could affect this. Upgrading is recomended though to prevent already resolved issues affecting you. Could you make sure that you don't have a few monitors for this? What are the logs?

deekerman commented

2026-02-28 04:10:16 -05:00

Author

Owner

@louislam commented on GitHub (Jan 26, 2026):

Yes, after reviewed #6745, I don't think it will introduce this bug. Plus I can't reproduce this issue on 2.1.0-beta.3.

@louislam commented on GitHub (Jan 26, 2026): Yes, after reviewed #6745, I don't think it will introduce this bug. Plus I can't reproduce this issue on 2.1.0-beta.3.