louislam/uptime-kuma

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

Open

#6041 opened on Aug 7, 2025

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (86,760 stars) (7,844 forks)batch import
A:notificationsfeature-requesthelp wanted

Description

📑 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

Contributor guide

Tech stack
javascriptnodejs
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptNode.jswebhooksuptime kuma notification system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
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.