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
Using listAllPersistentSubscriptions as a ping feels hacky, it's a side-effectful call that requires the persistent subscriptions feature to be available, and it may not accurately reflect the actual health of the connection...
A few questions:
Is there a dedicated healthcheck method (or low-overhead RPC call) available in the client that I may have missed?
Is there a getServerInfo / ping / checkHealth equivalent somewhere in the API?
If not, is a healthcheck utility on the roadmap?
KurrentDB exposes a /health/live HTTP endpoint, would it make sense to have the client expose a checkHealth() method backed by that, or by the gRPC equivalent?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi 👋
We're using the KurrentDB Node.js client in a production environment and we need a reliable way to check whether the connection to Kurrent is healthy
We currently use the following workaround, but we're not confident it's the right approach:
Using
listAllPersistentSubscriptionsas a ping feels hacky, it's a side-effectful call that requires the persistent subscriptions feature to be available, and it may not accurately reflect the actual health of the connection...A few questions:
getServerInfo/ping/checkHealthequivalent somewhere in the API?KurrentDB exposes a
/health/liveHTTP endpoint, would it make sense to have the client expose acheckHealth()method backed by that, or by the gRPC equivalent?Thanks! 🙏
Beta Was this translation helpful? Give feedback.
All reactions