mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Automatic Alert Suppression During Total Downtime #3672
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3672
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dancingmotion42 on GitHub (Oct 16, 2024).
📑 I have found these related issues/pull requests
Hi there,
I’d like to see a feature in Uptime Kuma that detects when all monitored services or ports are down at the same time. In such cases, the system should temporarily disable email alerts to prevent spamming everyone with notifications about the downtime. This way, if the Uptime Kuma server loses its internet connection, we won’t get flooded with unnecessary alerts.
Detection Logic:
User Notification:
🏷️ Feature Request Type
Maintenance, Other
🔖 Feature description
.
✔️ Solution
.
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Apr 27, 2025):
duplicate of the asked Conditional monitoring feature #1089