mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Scheduled Maintenance #118
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#118
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 @Kazer67 on GitHub (Aug 10, 2021).
Is your feature request related to a problem? Please describe.
For some services there's recurrent Scheduled Maintenance window (for example at 3am, services going down for 15 min for backup purpose).
Describe the solution you'd like
Ability to create Scheduled Maintenance (for example every day/day-of-the-week/month/years between 3h00 and 3h15) that I can affect to the monitor. When the monitor hit that time, it goes in "maintenance mode" which does or doesn't affect the overall uptime (depending if the "Affect Uptime" box is ticked) and it's logged as maintenance (and after 3h15 it goes back to normal monitoring).
@NickBootOne commented on GitHub (Aug 10, 2021):
Duplicated enhancement #191
DOWN/UP/... #910