mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
API to programmatically add and remove a maintenance window for a service #1791
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#1791
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 @miguelarios on GitHub (Jan 17, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
I have nightly Restic backups that set my Nextcloud instance to maintenance mode which causes an 503 error and notifies me via pushover as a critical notification since my Nextcloud instance is very important to me to keep up. I have set a recurring maintenance window during the backups but would be nice to have an api endpoint that I could curl as part of my bash script in my backup to add a maintenance for my Nextcloud instance to pause notifications.
🐻 Uptime-Kuma Version
1.19.3
💻 Operating System and Arch
Debian 5.10.149-2
🌐 Browser
Firefox 108.1
🐋 Docker Version
Docker 20.10.22
🟩 NodeJS Version
No response
@miguelarios commented on GitHub (Jan 17, 2023):
Out the wrong label on this. It needs to be a feature request. Sorry!
@Computroniks commented on GitHub (Jan 17, 2023):
Duplicate #118
@github-actions[bot] commented on GitHub (Apr 17, 2023):
We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.
@github-actions[bot] commented on GitHub (Apr 19, 2023):
This issue was closed because it has been stalled for 2 days with no activity.