mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
API Call for the number of monitors in error #1572
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#1572
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 @ArthurMitchell42 on GitHub (Nov 21, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
API
🔖 Feature description
It would be great to have an API call which returns a JSON structure containing at least the number of monitors in error and possibly the total number of monitors and/or the number that have been in error in a defined period.
The use I have for this is integrating it with the conky desktop information application which would allow an fast report right on the desktop for failures
✔️ Solution
host:port/api/status/all returning a JSON structure with the information
❓ Alternatives
I've thought of writing a Python script to loop through all possible monitor numbers but that would be bandwidth and resource intensive when polling significant numbers of monitors, also the numbers may not be co-linear?
📝 Additional Context
No response
@koen20 commented on GitHub (Nov 24, 2022):
Duplicate of https://github.com/louislam/uptime-kuma/issues/118
@ArthurMitchell42 commented on GitHub (Nov 30, 2022):
Hi, I'm not quite sure it's a duplicate, what I'm looking for is a bit more simple than a big change.
My solution was a script to scrape the metrics:
Regards,
A