mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Question related to disablement of single monitoring item via API #3015
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#3015
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 @blackseafisher on GitHub (Jan 10, 2024).
⚠️ Please verify that this question has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
At the moment, I am keeping track of several websites using Kuma. Backups are created during the night. In this timeframe, I wish to deactivate end-to-end monitoring with Kuma for specific websites.
Is it feasible to achieve this through the existing API?
If so, could you please guide me to the API call or provide a description for the relevant call?
Many thanks in advance!
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
na
💻 Operating System and Arch
na
🌐 Browser
na
🐋 Docker Version
na
🟩 NodeJS Version
na
@CommanderStorm commented on GitHub (Jan 10, 2024):
Currently, this is not possible through first party tooling.
See #118 for further details.
Current attempt at implementing this is https://github.com/louislam/uptime-kuma/pull/3854 which has been added to the
v2.1milestoneIn the meantime, please use third party tooling like https://uptime-kuma-api.readthedocs.io/