mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
api requests to Uptime Kuma #2421
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#2421
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 @JK-Effects on GitHub (Jul 28, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
Is there a way to address the Uptime Api to get maintenance windows and offline/online status?
This would allow to display information as a shoutout on other web pages or on a frontend when the backend is offline / in maintenance.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
Version: 1.22.1
💻 Operating System and Arch
Debian GNU/Linux 11 (bullseye)
🌐 Browser
Microsoft Edge Version 115.0.1901.183
🐋 Docker Version
Docker version 20.10.22
🟩 NodeJS Version
No response
@CommanderStorm commented on GitHub (Jul 28, 2023):
There currently is no api, see #118 and other duplicates like https://github.com/louislam/uptime-kuma/pull/1927
If you want to contribute (this is a community-driven project), our contribution guide and splitting https://github.com/louislam/uptime-kuma/pull/1834 would be starting points.
What we do offer however is the ability to get metrics via prometheus, which likely is sufficient for your usecase.
See the wiki-entry
@github-actions[bot] commented on GitHub (Oct 26, 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 (Oct 28, 2023):
This issue was closed because it has been stalled for 2 days with no activity.