Catching grpc connection configuration errors at startup
leefernandes opened this issue · comments
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?