Liveness probe

GET

/api/health/live

Answers 200 as soon as the process is serving HTTP. Performs no database, Redis or event-bus I/O, so it stays cheap at the frequency an orchestrator probes at and never fails because a dependency is down. Use this for container liveness probes; use GET /api/health for readiness and dependency status.

Responses

The process is up and serving requests

Content-Type

application/json

{

  

"status": "string",

  

"service": "string"

}

GET

/api/health/live

Samples