You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many infra management tools like K8s rely on a health check endpoint of service to schedule restart or do alerting. I guess we can GET /v1/checkpoints but not sure if that's hacky.
Why is it a good idea?
It'll be more compatible with existing infrastructures. Ogmios also has a /health endpoint.
Are you willing to work on it yourself?
I haven't dug much into the codebase to understand what should be considered healthy for Kupo.
The text was updated successfully, but these errors were encountered:
The GET /v1/checkpoints isn't hacky at all, it's meant to monitor the progress of the underlying syncing process. However, that's more about progress reporting than about health.
I agree that a health endpoint (and command, for containers) would be nice also.
Describe your idea, in simple words.
Many infra management tools like K8s rely on a health check endpoint of service to schedule restart or do alerting. I guess we can
GET /v1/checkpoints
but not sure if that's hacky.Why is it a good idea?
It'll be more compatible with existing infrastructures. Ogmios also has a
/health
endpoint.Are you willing to work on it yourself?
I haven't dug much into the codebase to understand what should be considered healthy for Kupo.
The text was updated successfully, but these errors were encountered: