louislam/uptime-kuma

broken upside down mode with (Push) monitors' notifcation detection of important heatbeats

Open

#5,911 建立於 2025年6月13日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)JavaScript (86,760 star) (7,844 fork)batch import
bughelp wanted

描述

📑 I have found these related issues/pull requests

I cannot find similer problem.

🏷️ Feature Request Type

Settings, Other

🔖 Feature description

I use reversed push alert, when the script triger it, the status goes down. While the team doesn't solve the issue, the script always triger the push url . This is generate to much notification, will be a better way, if the system send only one notification for one event. So the status goes DOWN, I got only one notification while the status goes UP I got another. But now I got one notification for UP events, but millions for DOWN events.

✔️ Solution

The system send only one notification when the status changed.

❓ Alternatives

No response

📝 Additional Context

No response

貢獻者指南

技術棧
javascriptnodejsvuesqlite
領域
backend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of Node.jsFamiliarity with uptime kuma's notification system
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Examine the notification sending logic, likely in files like 'server/notification.js' or similar. Understand how the current system detects status changes (e.g., UP/DOWN) and triggers notifications. Implement deduplication by tracking the last notification state per monitor, ensuring only one notification is sent per DOWN event until the status changes. Check existing comments for any discussed approaches or concerns. Consider using a database flag or in memory state to prevent multiple notifications for the same event.