mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Global maintenance window where uptime is not monitored? #908
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#908
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 @johanneskastl on GitHub (Mar 18, 2022).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
Sorry if this was raised before, I might be lacking the right key words.
Is it possible to set a daily/weekly window where machines are being rebooted and where downtime will be ignored?
I can set the retries option, so it only fails after some consecutive errors, but I need to configure that on every monitor. And it is not just in that specific time window, but also during normal operations, where I might get alerts quicker.
🐻 Uptime-Kuma Version
v1.11.1
💻 Operating System and Arch
not relevant, as Kubernetes only
🌐 Browser
Firefox
🐋 Docker Version
No response
🟩 NodeJS Version
No response
@koen20 commented on GitHub (Mar 18, 2022):
It is currently not possible to pause monitoring for a scheduled time. This is a duplicate of #191 .
Someone opened a pull request #1213 which adds this feature.
@johanneskastl commented on GitHub (Mar 18, 2022):
Thanks for the pointers, indeed I had the wrong key words for my search... :-)