App health checks

Mon, 01 Jan 0001 00:00:00 +0000

The app health checks feature allows probing for the health of your application and reacting to status changes.

Applications can become unresponsive for a variety of reasons. For example, your application:

Could be too busy to accept new work;
Could have crashed; or
Could be in a deadlock state.

Sometimes the condition can be transitory, for example:

If the app is just busy and will resume accepting new work eventually
If the application is being restarted for whatever reason and is in its initialization phase

App health checks are disabled by default. Once you enable app health checks, the Dapr runtime (sidecar) periodically polls your application via HTTP or gRPC calls. When it detects a failure in the app’s health, Dapr stops accepting new work on behalf of the application by:

Sidecar health

Mon, 01 Jan 0001 00:00:00 +0000

Dapr provides a way to determine its health using an HTTP /healthz endpoint. With this endpoint, the daprd process, or sidecar, can be:

Probed for its overall health
Probed for Dapr sidecar readiness from infrastructure platforms
Determined for readiness and liveness with Kubernetes

In this guide, you learn how the Dapr /healthz endpoint integrates with health probes from the application hosting platform (for example, Kubernetes) as well as the Dapr SDKs.

Health checks on Dapr Docs

App health checks

Sidecar health