louislam/uptime-kuma

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

Open

#5911 opened on Jun 13, 2025

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (86,760 stars) (7,844 forks)batch import
bughelp wanted

Description

📑 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
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of Node.jsFamiliarity with uptime kuma's notification system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
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.