Replies: 1 comment
-
|
Looks like someone has this #11263 which adds /health along with some other items |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Context
ComfyUI currently exposes a
/system_statsendpoint which provides useful runtime and system-level information. However, it is not ideal for external monitoring tools that expect a lightweight, standardized health check endpoint.Many homelab dashboards and service monitors (e.g. Homepage’s siteMonitor integration https://gethomepage.dev/) expect a simple HTTP endpoint that returns a minimal “up/down” status response without additional parsing or overhead.
Problem
/system_statsis not well-suited for health monitoring because:It returns detailed system metrics rather than a simple status indicator
It may change shape or size depending on implementation updates
External tools must infer health indirectly instead of checking explicitly
It is not aligned with common conventions used by container orchestrators and monitoring systems
As a result, integrating ComfyUI into dashboards like Homepage, Uptime Kuma, or Kubernetes probes requires workarounds.
Proposed Solution
Introduce a dedicated lightweight endpoint:
Response
{ "status": "healthy", "timestamp": "2026-06-06T18:13:42.684521" }Optional Enhancements (future considerations)
While the initial version should remain minimal, future extensions could include:
"status": "degraded"when dependencies are available but suboptimal"status": "unhealthy"for internal failure statesBenefits
Compatibility
Summary
A dedicated
/healthendpoint would provide a clean, standardized way to monitor ComfyUI instances in homelabs and production-like environments, improving integration with modern dashboards and infrastructure tooling while keeping the API surface clean and predictable.Beta Was this translation helpful? Give feedback.
All reactions