A health check lets an orchestrator assess whether an application is ready to interact with other systems. Aspire does this by sending HTTP requests to health-check endpoints and evaluating their responses. section 6.5.2 section 6.7
A minimal self-check returns a healthy result while the application is running. If the application fails, the endpoint becomes inaccessible rather than returning a status. section 6.5.2
builder.Services.AddHealthChecks()
.AddCheck("self", () => HealthCheckResult.Healthy(), ["live"]);
Register a self-check and tag it live so an endpoint can select it. section 6.5.2
Map endpoints for different health-check uses:
- Use /health as the basic health-check endpoint. section 6.5.3
- Use /alive to check for a response that includes the live tag. section 6.5.3
Run health checks in production as well as development, using the same endpoint paths. Because these endpoints are publicly accessible like other HTTP endpoints, protect them as the deployment requires. Runtime checks help monitor services but do not replace tests before production. section 6.5.4
