mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
API-Function for overall status or status of a page #1741
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#1741
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 @wortkrieg on GitHub (Jan 6, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
API
🔖 Feature description
I'm looking for an API function to get the state of all my monitors (just if they're working as expected or if there are any issues). Just like the information I get on top of every status page I create with the green check icon.
I'd love to include that information on an overall overview page and for having an idea if everything works well at a glance.
✔️ Solution
add another API endpoint, like it's done for badges. But for the overall system / status page status.
❓ Alternatives
Setting up conditional monitors as described here https://github.com/louislam/uptime-kuma/issues/2487 could also work.
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Jul 3, 2023):
@wortkrieg
Is this a duplicate of #118 ?
If no, what justifies this as a distinct issue?
If yes, could you close this issue? (duplicates only create immortal zombies and are hard to issue-manage)