louislam/uptime-kuma

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

Open

#5.911 geöffnet am 13. Juni 2025

Auf GitHub ansehen
 (5 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)JavaScript (86.760 Stars) (7.844 Forks)batch import
bughelp wanted

Beschreibung

📑 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

Contributor Guide

Tech Stack
javascriptnodejsvuesqlite
Domain
backend
Issue Type
feature
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
half day
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
active
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
clear
Voraussetzungen
Basic knowledge of Node.jsFamiliarity with uptime kuma's notification system
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
65
Research-Richtung
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.