Does temporal server have any healthcheck endpoint? How can I set up the target groups to hit temporal’s gRPC endpoints? I see from aws docs - Health checks for your target groups - Elastic Load Balancing The destination for health checks on the targets. If the protocol version is HTTP/1.1 or HTT…

After some investigation I think the right path would be: /grpc.health.v1.Health/Check If you set service field in request message to temporal.api.workflowservice.v1.WorkflowService. it should reply with: { "status": "SERVING" } but even if you don’t, it looks like health check responds with 2…

Probably the easiest way to go here is to pass a health check by opening a tcp connection to the grpc service endpoint - if you can connect its “healthy”

I’m not so familiar with gRPC. Coming from mostly HTTP RESTful endpoints. What’s the “grpc service endpoint” you are referring to? I was expecting something equivalent to /healthcheck for http endpoints.

we don’t have a real grpc health check right now - so best recommendation is just to try and open a connection. the grpc service endpoint i’m talking about is just the temporal endpoint you’d point your client sdk to.

doh - so i was wrong here. temporal itself does have grpc health checks but we’re not using them in our helm charts and instead do a tcp check. for health checks using target groups you can set the path to: /temporal.api.workflowservice.v1.WorkflowService/Check My apologies for steering you wrong …

Hey @derek , thanks for the follow up. I tried the path you mentioned, but it appears that the target group is failing. Not sure if that path exists. I tried to look up api/service.proto at master · temporalio/api · GitHub to see if such a healthcheck endpoint exists but found nothing. Here’s my t…

Did you get it to work just over HTTP2? How did you get it to work, can you provide curl call?

Just to confirm, with these health checks, should I be able to hit any of the services on “ service.name.com:7233/grpc.health.v1.Health/Check ” ? Struggling to find the correct combination to make AWS Application Load Balancers happy. Looks like they expect an HTTP response though… hmm curl 172.17.0…

Just to confirm, with these health checks, should I be able to hit any of the services on “ service.name.com:7233/grpc.health.v1.Health/Check ” ? Each temporal server service type has default grpc port (see here ) which you can change if you needed. Note that the worker service does not expose a hea…

OK, so if I make the GPRC ports available via a network load balancer, that part will work. And I can easily give them a consistent name via DNS. What about the membership ports? I’m unclear on what the local networking requirements are / how the broadcast address comes into play when running these…

Deploying in AWS - healthchecks

Community Support

Shawn_Lim June 24, 2021, 7:47am 8

thanks this works now!

Health Check / Ping Temporal Frontend via grpcurl

Topic		Replies	Views
Health Check / Ping Temporal Frontend via grpcurl Community Support healthcheck	1	2040	July 22, 2021
Exposing grpc Frontend via ALB Community Support helm , general-impl , configuration , deployment	4	2612	June 20, 2022
AWS EKS deployment, gRPC health check failing Community Support go-sdk , aws	3	1861	October 28, 2021
Temporal Server Health Check Community Support production	6	10005	January 13, 2024
Unable to run temporal in Knative/Google Cloud Run Community Support	6	2372	May 20, 2021

Deploying in AWS - healthchecks

Related topics