App engine readiness / liveness probe path

[yuan1021]

Hello,

We are currently using App Engine for deploying our Node.js applications (microservices using the Moleculer framework). I would like to know whether it is feasible to provide an absolute URL path or a customized run script for readiness/liveness probes ?

Thanks a lot.

[Marramirez]

Hi @yuan1021,

Welcome to the Google Cloud Community!

Yes, It's possible to provide a URL path.

In App Engine, split health checks are enabled by default. However, HTTP requests from health checks are not forwarded to your application by default. You have to specify the path for liveness checks and readiness checks.

You can configure your App.yaml file to extend health checks for your application.

• Liveness Checks
• Readiness Checks

If the above option doesn't work, you can contact Google Cloud Support to further look into your case. Let me know if it helped, thanks!

[yuan1021]

Thanks for your reply.

I have already checked the official reference regarding liveness and readiness checks. However, it seems that the `path` property is a relative path based on localhost or the local machine. What can I do if my application needs to expose the health check endpoints on a different port, which is not the default 8080 ?

For instance, one of the applications exposes two probe routes: `localhost:3000/live` and `localhost:3000/ready`. I have tried to set the `path` as `"http://localhost:3000/ready"`, but the deployment failed, and the log displayed a readiness check using `"/http://localhost:3000/ready"`.

Thank you.