aspire-service-defaults

You can centralize OpenTelemetry configuration across .NET Aspire services by creating a shared ServiceDefaults project that applies consistent OTLP exporter setup, health checks, and resilience policies to all API, Worker, and AppHost projects.

The AddServiceDefaults pattern in .NET Aspire is a shared configuration method that enforces unified OpenTelemetry observability, service discovery, HTTP resilience, and health check endpoints across distributed API, Worker, and AppHost services.

Shared health checks for Aspire API and Worker services are set up by distributing a centralized ServiceDefaults configuration that calls MapDefaultEndpoints, ensuring consistent readiness and liveness monitoring across all distributed services.

Yes, the .NET Aspire ServiceDefaults setup supports service discovery and HTTP resilience by integrating cross-service address resolution and built-in retry with circuit-breaker policies automatically through the AddServiceDefaults extension method.

The best way to standardize observability and OTLP exporter configuration in Aspire is to automate a shared ServiceDefaults project that enforces consistent OpenTelemetry setup across all distributed API, Worker, and AppHost services.