mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Scheduled downtime #557
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#557
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 @federicotravaini on GitHub (Nov 13, 2021).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
New Monitor
🔖 Feature description
I have servers that have scheduled downtime for maintenance and it would help to set the scheduled downtime so it doesn't notify me for nothing.
✔️ Solution
A server/service/device shuts down every night for 1 hour and I receive every night a notification that the device is down, and then back up. I suggest we set the expected uptime hours/minutes for every service (should me very detailed, like hours, days of the week, months, etc.)
❓ Alternatives
No response
📝 Additional Context
No response
@deefdragon commented on GitHub (Nov 13, 2021):
Duplicate of #900 (#233) for scheduled downtime for notifications, and #191 for periodic scheduled downtime