mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
No-Send notification option #725
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#725
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 @LeSupaPoney on GitHub (Jan 7, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
Other
🔖 Feature description
Hello,
Add an option to temporarily disable notifications between 2 moments.
I have an important server that I have to monitore every 20seconds but every night I have to reboot it.
It takes about 2 minutes to be up again.
✔️ Solution
Example:
When create/edit notification, a case "Disable between" to check and 2 boxes: 2:40am / 03:00am
So if the server is down at 2:40am it will not notify, and after 03:00am it reworks as usual
❓ Alternatives
No response
📝 Additional Context
No response
@chakflying commented on GitHub (Jan 7, 2022):
Duplicate of #191
@LeSupaPoney commented on GitHub (Jan 7, 2022):
Oops my bad, I checked and did not found it, thanks.
Sorry