mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Scheduled Down Monitors #915
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#915
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 @athornfam2 on GitHub (Mar 20, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature
🔖 Feature description
I have several platforms and servers that are not online 24/7/365 due to costs for that service and only run during hours of operation (8:00 AM to 5:00 PM). Of course, this tool is to notify in an outage but it would be nice to have scheduled monitoring so I don't get alarms at 10:00 PM constantly but having all the nice monitoring when needed.
✔️ Solution
Add a setting in each monitor to setup scheduled monitoring during the creation of the new monitor and after the monitor has been created. Checkbox to enable and time range to monitor during.
❓ Alternatives
No response
📝 Additional Context
No response
@koen20 commented on GitHub (Mar 20, 2022):
This is a duplicate of #191
Someone opened a pull request https://github.com/louislam/uptime-kuma/pull/1213 which adds adds a maintenance planning system.
@athornfam2 commented on GitHub (Mar 20, 2022):
@koen20 Oh... I did not look back that far. I guess this can be closed out and I'll add input to that request.