louislam/uptime-kuma

Add unique IDs to stack field notifications to prevent dropping "duplicate" messages

Open

#6,041 建立於 2025年8月7日

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

描述

📑 I have found these related issues/pull requests

There are some issues regarding failing monitors. But I did not find issues with webhooks being dropped by the receiving api which may look like a failing monitor.

🏷️ Feature Request Type

API / automation options

🔖 Feature description

At least the stackfield notification type seems to not sending a unique id in its webhook. The stackfield API we send this to does not accept recurring messages, so if a monitor goes down and up multiple times the webhook message is being dropped.

✔️ Solution

It would be nice if the webhook could send a hidden unique id in each of its json message. Maybe something like a unix time stamp.

❓ Alternatives

No response

📝 Additional Context

No response

貢獻者指南

技術棧
javascriptnodejs
領域
backendapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaScriptNode.jswebhooksuptime kuma notification system
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
The fix likely requires modifying the stackfield notification provider in uptime kuma's source code, probably under server/notification providers/stackfield.js. Add a unique identifier field (e.g., 'id': Date.now() or a UUID) to the JSON payload sent in the webhook request. Ensure the field is not already present and is backward compatible. Test with a local uptime kuma instance and a webhook receiver to confirm duplicates are no longer dropped.