aspire-service-defaults

Centralize OpenTelemetry, health checks, service discovery, and HTTP resilience for .NET Aspire microservices.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill aspire-service-defaults-agibuild
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-service-defaults
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/aspire-service-defaults
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill aspire-service-defaults-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill centralizes common configuration for .NET Aspire microservices, ensuring consistent observability, health checks, and resilience across your distributed application.

Core Features & Use Cases

  • Unified Observability: Integrates OpenTelemetry for logging, tracing, and metrics.
  • Standardized Health Checks: Provides ready and liveness endpoints.
  • Resilience & Discovery: Configures HTTP client resilience policies and service discovery.
  • Use Case: When building a new microservice in an Aspire application, use this Skill to quickly add standardized OpenTelemetry and health check configurations by calling AddServiceDefaults().

Quick Start

Add the aspire-service-defaults skill to your .NET Aspire service project.

Frequently Asked Questions about aspire-service-defaults

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure OpenTelemetry and health checks for .NET Aspire microservices?

To configure OpenTelemetry and health checks for .NET Aspire microservices, you can apply centralized service defaults by calling AddServiceDefaults() to ensure unified observability and standardized liveness endpoints.

What is the best way to standardize service discovery and HTTP resilience in Aspire?

Standardizing service discovery and HTTP resilience in Aspire involves applying a centralized service defaults configuration to distributed applications, ensuring robust inter-service communication and consistent resilience policies.

Do I need specific NuGet packages to set up Aspire service defaults?

Yes, integrating Aspire service defaults requires the .NET Aspire SDK and specific NuGet packages to properly configure OpenTelemetry, health checks, and service discovery within your distributed application.

How does AddServiceDefaults() work when building a new microservice in Aspire?

AddServiceDefaults() works by applying a centralized configuration extension to your .NET Aspire project, automatically injecting logging, tracing, metrics, and health check endpoints for that microservice.

When do I need centralized service defaults for my distributed application?

You need centralized service defaults for your distributed application when multiple microservices require consistent observability, health checks, and HTTP resilience policies to maintain robust inter-service communication.

Can I use service defaults for both liveness and readiness health checks in Aspire?

Yes, applying standardized Aspire service defaults provides both ready and liveness health check endpoints, ensuring your distributed application consistently reports service health status.