aspire-service-defaults

You can unify OpenTelemetry and health checks across Aspire services by referencing a shared ServiceDefaults project. Calling AddServiceDefaults() in API or Worker startup applies uniform observability, health readiness, and service discovery configurations.

Standardizing HTTP resilience and service discovery in .NET Aspire distributed apps is achieved through a shared ServiceDefaults project. It provides built-in resilience policies and discovery mechanisms uniformly consumed by API, Worker, and AppHost projects.

To add service defaults to Aspire API and Worker projects, call AddServiceDefaults() in your startup configuration. This single method wires in centralized OpenTelemetry, ready/live health checks, service discovery, and HTTP resilience policies.

Yes, you can use a shared ServiceDefaults project for both API and Worker services in Aspire. It applies uniformly across distributed app components, enabling consistent telemetry, health readiness, and HTTP resilience without duplicating configurations.

Separate ready and live health checks in Aspire service defaults differentiate between application availability and dependency readiness. This separation ensures consistent health monitoring across API and Worker services, preventing routing traffic to unprepared instances.