starred/uptime-kuma

Fork 0

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

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

New issue

Open

opened 2026-02-28 03:55:56 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 03:55:56 -05:00

Owner

Originally created by @LightningRhino on GitHub (Aug 7, 2025).

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

Originally created by @LightningRhino on GitHub (Aug 7, 2025). ### 📑 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_

deekerman added the

feature-request

A:notifications

help wanted

labels

2026-02-28 03:55:56 -05:00

deekerman commented

2026-02-28 03:56:01 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Aug 7, 2025):

Feel free to provide us with an pr adding time based uuids to the to that notification provider.
Because of the amount of providers we have, this is not something that we can do, but if you do a PR with the nessesary screenshots that this is fixed afterwards, I can merge it.

@CommanderStorm commented on GitHub (Aug 7, 2025): Feel free to provide us with an pr adding time based uuids to the to that notification provider. Because of the amount of providers we have, this is not something that we can do, but if you do a PR with the nessesary screenshots that this is fixed afterwards, I can merge it.

deekerman commented

2026-02-28 03:56:01 -05:00

Author

Owner

@LightningRhino commented on GitHub (Aug 7, 2025):

Thank you for your answer.
But I think this is beyond my capabilities.
Maybe you could keep this as a suggestion for future updates.

@LightningRhino commented on GitHub (Aug 7, 2025): Thank you for your answer. But I think this is beyond my capabilities. Maybe you could keep this as a suggestion for future updates.

deekerman commented

2026-02-28 03:56:01 -05:00

Author

Owner

@DeborahOlaboye commented on GitHub (Jan 14, 2026):

Hi @CommanderStorm , Can I work on this issue?

@DeborahOlaboye commented on GitHub (Jan 14, 2026): Hi @CommanderStorm , Can I work on this issue?

deekerman commented

2026-02-28 03:56:01 -05:00

Author

Owner

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

Shure, but please make sure to attach the screenshots to the PR that we require to ensure that you tested that this works

@CommanderStorm commented on GitHub (Jan 14, 2026): Shure, but please make sure to attach the screenshots to the PR that we require to ensure that you tested that this works

deekerman commented

2026-02-28 03:56:01 -05:00

Author

Owner

@DeborahOlaboye commented on GitHub (Jan 14, 2026):

Alright, thank you.

@DeborahOlaboye commented on GitHub (Jan 14, 2026): Alright, thank you.