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
Please demonstrate or explain the recommended pattern for catching ClientConn configuration errors (such as incorrect target value) at startup time of an application. A simple check that the server can be reached given the target and dial options.
Using health/grpc_health_v1 is the recommended way but it requires servers to implement Check method and return a meaningful response where as ClientConn Connect can do a simple connectivity check without requiring any server implementation. However, ClientConn Connect doesn't provide any health status of the service
Please demonstrate or explain the recommended pattern for catching ClientConn configuration errors (such as incorrect target value) at startup time of an application. A simple check that the server can be reached given the target and dial options.
Would it be recommended to use the health/grpc_health_v1 package, ClientConn Connect, or another approach?
The text was updated successfully, but these errors were encountered: