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.