mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Feature Request: Monitoring endpoint /health #3973
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#3973
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 @mabed-fr on GitHub (Feb 14, 2025).
📑 I have found these related issues/pull requests
no
🏷️ Feature Request Type
Other
🔖 Feature description
Can you add in /heath endpoint which checks that the kuma uptime components are ok?
This would make it possible to better monitor monitoring
✔️ Solution
/heath
❓ Alternatives
No response
📝 Additional Context
No response
@paul-uz commented on GitHub (Feb 16, 2025):
Could we then use kuma to check kuma? 🤔
@mabed-fr commented on GitHub (Feb 16, 2025):
Yes other uptime kuma in other region or free SAS services or uptime kuma friend
@paul-uz commented on GitHub (Feb 16, 2025):
How deep down the rabbit hole do you go? 🤔
@mabed-fr commented on GitHub (Feb 16, 2025):
I'm not going into depth, but my Uptime Kuma monitors critical services, so I'm keeping an eye on it with a SAS service (Uptime Robot free plan) and that's about it, to be honest.
@paul-uz commented on GitHub (Feb 16, 2025):
I was making a joke about kuma monitoring kuma monitoring kuma monitoring kuma etc etc
@mabed-fr commented on GitHub (Feb 16, 2025):
Yes my bad :)
@emilcondrea commented on GitHub (Mar 1, 2025):
This would be super useful, currently I am looking for missing metrics to detect monitors are down but would be really useful to use a liveness probe with a /health endpoint.
@CommanderStorm commented on GitHub (Apr 15, 2025):
We have a healthcheck that our dockerfile registers.
We just query localhost.
github.com/louislam/uptime-kuma@13a85b8200/extra/healthcheck.go (L71)Usually, that catches all erros and is reasonably performant.