-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose health check on WorkflowClient #595
Comments
Waiting on SDK consensus here. |
There is checkHealth method which is invoked at the time of client creation, but it is private (go.temporal.io/sdk@v1.12.0/internal/client.go) |
@guptamridul1809 - This is no longer invoked on client creation in the current version (we invoke another call). But yes, this issue is for exposing that call to be called explicitly. |
Temporal SDK should expose a method like WorkflowServiceStubs#healthCheck or WorkflowServiceStubs#isHealthy that allows users to check if the WorkflowClient/WorkflowServiceStubs underlying channel / connection to Temporal server is healthy.
There were quite a bit of user requests for such a method from users for all SDKs.
Having this method on Stubs is preferable over WorkflowClient, because it's the lowest level abstraction on top of the channel and WorkflowClient can just fall back on the WorkflowServiceStubs method. But if the language doesn't have a wrapper for stubs (like Java does), this method may be on WorkflowClient.
Issues for other SDKs:
temporalio/sdk-java#828
temporalio/sdk-typescript#312
The text was updated successfully, but these errors were encountered: