CommunityCodierung & Entwicklunggithub.com

aspire-service-defaults

Erstellt ein gemeinsames ServiceDefaults-Projekt für Aspire-Anwendungen. Zentralisiert Konfiguration für OpenTelemetry, Health Checks, Resilienz und Service Discovery über alle Dienste hinweg.

Was ist aspire-service-defaults?

Dieses Skill erstellt ein gemeinsames 'ServiceDefaults'-Projekt für Aspire-Anwendungen, das die Basiskonfiguration für alle Dienste einer verteilten Anwendung zentralisiert. Es bietet standardisierte OpenTelemetry-Integration (Logging, Tracing, Metriken), Health Checks (Liveness/Readiness), Service Discovery und HTTP-Resilienz (Retry, Circuit Breaker) über die Methode `AddServiceDefaults()`. Entwickler sparen erheblich Zeit, da sie nicht in jedem Dienst die gleiche Observability- und Ausfallsicherheitslogik manuell konfigurieren müssen. Das Skill unterstützt Aspire-Anwendungen mit .NET 9 und zeigt detailliert, wie das Projekt aufgebaut wird, wie eigene Health Checks und Trace Sources hinzugefügt werden und wie die Health-Endpunkte in Produktion geschützt werden können. Es ist ideal für Teams, die konsistente und wartbare Aspire-Anwendungen bauen möchten.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Aaronontheweb/dotnet-skills/tree/main/skills/aspire-service-defaults

Installed? Explore more Codierung & Entwicklung skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Aspire Service Defaults

Wann dieses Skill verwenden

Verwende dieses Skill, wenn:

  • Du Aspire-basierte verteilte Anwendungen entwickelst
  • Du konsistente Observability (Logging, Tracing, Metriken) über mehrere Dienste hinweg benötigst
  • Du eine gemeinsame Health-Check-Konfiguration haben möchtest
  • Du HttpClient-Resilienz und Service Discovery konfigurieren möchtest

Was sind ServiceDefaults?

ServiceDefaults ist ein gemeinsames Projekt, das die Basiskonfiguration für alle Dienste einer Aspire-Anwendung bereitstellt:

  • OpenTelemetry - Logging, Tracing und Metriken
  • Health Checks - Readiness- und Liveness-Endpunkte
  • Service Discovery - Automatische Service-Auflösung
  • HTTP-Resilienz - Retry- und Circuit-Breaker-Richtlinien

Jeder Dienst referenziert dieses Projekt und ruft AddServiceDefaults() auf.


Projektstruktur

src/
  MyApp.ServiceDefaults/
    Extensions.cs
    MyApp.ServiceDefaults.csproj
  MyApp.Api/
    Program.cs  # Ruft AddServiceDefaults() auf
  MyApp.Worker/
    Program.cs  # Ruft AddServiceDefaults() auf
  MyApp.AppHost/
    Program.cs

ServiceDefaults-Projekt

Projektdatei

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net9.0</TargetFramework>
    <IsAspireSharedProject>true</IsAspireSharedProject>
  </PropertyGroup>

  <ItemGroup>
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
    <PackageReference Include="Microsoft.Extensions.Http.Resilience" />
    <PackageReference Include="Microsoft.Extensions.ServiceDiscovery" />
    <PackageReference Include="OpenTelemetry.Exporter.OpenTelemetryProtocol" />
    <PackageReference Include="OpenTelemetry.Extensions.Hosting" />
    <PackageReference Include="OpenTelemetry.Instrumentation.AspNetCore" />
    <PackageReference Include="OpenTelemetry.Instrumentation.Http" />
    <PackageReference Include="OpenTelemetry.Instrumentation.Runtime" />
  </ItemGroup>
</Project>

Extensions.cs

using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Diagnostics.HealthChecks;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Diagnostics.HealthChecks;
using Microsoft.Extensions.Logging;
using OpenTelemetry;
using OpenTelemetry.Metrics;
using OpenTelemetry.Trace;

namespace Microsoft.Extensions.Hosting;

public static class Extensions
{
    private const string HealthEndpointPath = "/health";
    private const string AlivenessEndpointPath = "/alive";

    /// <summary>
    /// Fügt gemeinsame Aspire-Dienste hinzu: OpenTelemetry, Health Checks,
    /// Service Discovery und HTTP-Resilienz.
    /// </summary>
    public static TBuilder AddServiceDefaults<TBuilder>(this TBuilder builder)
        where TBuilder : IHostApplicationBuilder
    {
        builder.ConfigureOpenTelemetry();
        builder.AddDefaultHealthChecks();

        builder.Services.AddServiceDiscovery();

        builder.Services.ConfigureHttpClientDefaults(http =>
        {
            // Resilienz: Wiederholungen, Circuit Breaker, Timeouts
            http.AddStandardResilienceHandler();

            // Service Discovery: Dienstnamen in Adressen auflösen
            http.AddServiceDiscovery();
        });

        return builder;
    }

    public static TBuilder ConfigureOpenTelemetry<TBuilder>(this TBuilder builder)
        where TBuilder : IHostApplicationBuilder
    {
        // Logging
        builder.Logging.AddOpenTelemetry(logging =>
        {
            logging.IncludeFormattedMessage = true;
            logging.IncludeScopes = true;
        });

        builder.Services.AddOpenTelemetry()
            // Metriken
            .WithMetrics(metrics =>
            {
                metrics
                    .AddAspNetCoreInstrumentation()
                    .AddHttpClientInstrumentation()
                    .AddRuntimeInstrumentation();
            })
            // Tracing
            .WithTracing(tracing =>
            {
                tracing
                    .AddSource(builder.Environment.ApplicationName)
                    .AddAspNetCoreInstrumentation(options =>
                        // Health Checks von Traces ausschließen
                        options.Filter = context =>
                            !context.Request.Path.StartsWithSegments(HealthEndpointPath) &&
                            !context.Request.Path.StartsWithSegments(AlivenessEndpointPath))
                    .AddHttpClientInstrumentation();
            });

        builder.AddOpenTelemetryExporters();

        return builder;
    }

    private static TBuilder AddOpenTelemetryExporters<TBuilder>(this TBuilder builder)
        where TBuilder : IHostApplicationBuilder
    {
        // OTLP-Exporter verwenden, wenn Endpunkt konfiguriert ist (Aspire Dashboard, Jaeger, etc.)
        var useOtlp = !string.IsNullOrWhiteSpace(
            builder.Configuration["OTEL_EXPORTER_OTLP_ENDPOINT"]);

        if (useOtlp)
        {
            builder.Services.AddOpenTelemetry().UseOtlpExporter();
        }

        return builder;
    }

    public static TBuilder AddDefaultHealthChecks<TBuilder>(this TBuilder builder)
        where TBuilder : IHostApplicationBuilder
    {
        builder.Services.AddHealthChecks()
            .AddCheck("self", () => HealthCheckResult.Healthy(), ["live"]);

        return builder;
    }

    /// <summary>
    /// Mappt Health Check Endpunkte. Nach UseRouting() aufrufen.
    /// </summary>
    public static WebApplication MapDefaultEndpoints(this WebApplication app)
    {
        // Nur in Entwicklungsumgebung verfügbar – siehe Sicherheitshinweis unten
        if (app.Environment.IsDevelopment())
        {
            // Readiness: Alle Health Checks müssen bestehen
            app.MapHealthChecks(HealthEndpointPath);

            // Liveness: Nur "live"-getaggte Prüfungen
            app.MapHealthChecks(AlivenessEndpointPath, new HealthCheckOptions
            {
                Predicate = r => r.Tags.Contains("live")
            });
        }

        return app;
    }
}

Verwendung in Diensten

API-Dienst

var builder = WebApplication.CreateBuilder(args);

// Alle Service Defaults hinzufügen
builder.AddServiceDefaults();

// Eigene Dienste hinzufügen
builder.Services.AddControllers();

var app = builder.Build();

// Health-Endpunkte mappen
app.MapDefaultEndpoints();

app.MapControllers();
app.Run();

Worker-Dienst

var builder = Host.CreateApplicationBuilder(args);

// Funktioniert auch für Nicht-Web-Hosts
builder.AddServiceDefaults();

builder.Services.AddHostedService<MyWorker>();

var host = builder.Build();
host.Run();

Eigene Health Checks hinzufügen

public static TBuilder AddDefaultHealthChecks<TBuilder>(this TBuilder builder)
    where TBuilder : IHostApplicationBuilder
{
    builder.Services.AddHealthChecks()
        // Grundlegende Liveness
        .AddCheck("self", () => HealthCheckResult.Healthy(), ["live"])

        // Datenbank-Readiness
        .AddNpgSql(
            builder.Configuration.GetConnectionString("postgres")!,
            name: "postgres",
            tags: ["ready"])

        // Redis-Readiness
        .AddRedis(
            builder.Configuration.GetConnectionString("redis")!,
            name: "redis",
            tags: ["ready"])

        // Eigener Check
        .AddCheck<MyCustomHealthCheck>("custom", tags: ["ready"]);

    return builder;
}

Eigene Trace-Quellen hinzufügen

Für Akka.NET oder benutzerdefinierte ActivitySources:

public static TBuilder ConfigureOpenTelemetry<TBuilder>(this TBuilder builder)
    where TBuilder : IHostApplicationBuilder
{
    builder.Services.AddOpenTelemetry()
        .WithTracing(tracing =>
        {
            tracing
                .AddSource(builder.Environment.ApplicationName)
                // Akka.NET Tracing
                .AddSource("Akka.NET")
                // Eigene Quellen
                .AddSource("MyApp.Orders")
                .AddSource("MyApp.Payments")
                .AddAspNetCoreInstrumentation()
                .AddHttpClientInstrumentation();
        });

    return builder;
}

Health Checks in der Produktion

Schütze Health-Endpunkte in der Produktion oder verwende andere Pfade:

public static WebApplication MapDefaultEndpoints(this WebApplication app)
{
    // Immer für Kubernetes-Probes mappen, aber beachte:
    // - Verwendung interner Ports
    // - Hinzufügen einer Autorisierung
    // - Ratenbegrenzung

    app.MapHealthChecks("/health", new HealthCheckOptions
    {
        // Nur Status zurückgeben, keine Details
        ResponseWriter = (context, report) =>
        {
            context.Response.ContentType = "text/plain";
            return context.Response.WriteAsync(report.Status.ToString());
        }
    });

    app.MapHealthChecks("/alive", new HealthCheckOptions
    {
        Predicate = r => r.Tags.Contains("live"),
        ResponseWriter = (context, report) =>
        {
            context.Response.ContentType = "text/plain";
            return context.Response.WriteAsync(report.Status.ToString());
        }
    });

    return app;
}

Integration mit AppHost

Der AppHost konfiguriert automatisch OTLP-Endpunkte:

// AppHost/Program.cs
var builder = DistributedApplication.CreateBuilder(args);

var postgres = builder.AddPostgres("postgres");
var redis = builder.AddRedis("redis");

var api = builder.AddProject<Projects.MyApp_Api>("api")
    .WithReference(postgres)
    .WithReference(redis);

builder.Build().Run();

Dienste erhalten automatisch OTEL_EXPORTER_OTLP_ENDPOINT und senden Telemetriedaten an das Aspire Dashboard.


Best Practices

PraxisGrund
Ein ServiceDefaults-ProjektKonsistente Konfiguration über alle Dienste hinweg
Health Checks von Traces filternReduziert Rauschen in Observability-Daten
Health Checks taggenLiveness von Readiness trennen
StandardResilienceHandler verwendenIntegrierte Wiederholungen, Circuit Breaker, Timeouts
Eigene Trace-Quellen hinzufügenDomain-spezifische Spans erfassen

Ressourcen

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

akka-hosting-actor-patterns

Patterns for building entity actors with Akka.Hosting - GenericChildPerEntityParent, message extractors, cluster sharding abstraction, akka-reminders, and ITimeProvider. Supports both local testing and clustered production modes.

akka-net-aspire-configuration

Configure Akka.NET with .NET Aspire for local development and production deployments. Covers actor system setup, clustering, persistence, Akka.Management integration, and Aspire orchestration patterns.

akka-net-best-practices

Critical Akka.NET best practices including EventStream vs DistributedPubSub, supervision strategies, error handling, Props vs DependencyResolver, work distribution patterns, and cluster/local mode abstractions for testability.

akka-net-management

Akka.Management for cluster bootstrapping, service discovery (Kubernetes, Azure, Config), health checks, and dynamic cluster formation without static seed nodes.

akka-net-testing-patterns

Write unit and integration tests for Akka.NET actors using modern Akka.Hosting.TestKit patterns. Covers dependency injection, TestProbes, persistence testing, and actor interaction verification. Includes guidance on when to use traditional TestKit.

api-design

Design stable, compatible public APIs using extend-only design principles. Manage API compatibility, wire compatibility, and versioning for NuGet packages and distributed systems.

aspire-configuration

Configure Aspire AppHost to emit explicit app config via environment variables; keep app code free of Aspire clients and service discovery.

aspire-integration-testing

Write integration tests using .NET Aspire

crap-analysis

Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code. Use OpenCover format with ReportGenerator for Risk Hotspots showing cyclomatic complexity and untested code paths.

csharp-concurrency-patterns

Choosing the right concurrency abstraction in .NET - from async/await for I/O to Channels for producer/consumer to Akka.NET for stateful entity management. Avoid locks and manual synchronization unless absolutely necessary.

database-performance

Database access patterns for performance. Separate read/write models, avoid N+1 queries, use AsNoTracking, apply row limits, and never do application-side joins. Works with EF Core and Dapper.

dependency-injection-patterns

Organize DI registrations using IServiceCollection extension methods. Group related services into composable Add* methods for clean Program.cs and reusable configuration in tests.

dotnet-devcert-trust

Diagnose and fix .NET HTTPS dev certificate trust issues on Linux. Covers the full certificate lifecycle from generation to system CA bundle inclusion, with distro-specific guidance for Ubuntu, Fedora, Arch, and WSL2.

dotnet-local-tools

Managing local .NET tools with dotnet-tools.json for consistent tooling across development environments and CI/CD pipelines.

dotnet-project-structure

Modern .NET project structure including .slnx solution format, Directory.Build.props, central package management, SourceLink, version management with RELEASE_NOTES.md, and SDK pinning with global.json.

dotnet-slopwatch

Use Slopwatch to detect LLM reward hacking in .NET code changes. Run after every code modification to catch disabled tests, suppressed warnings, empty catch blocks, and other shortcuts that mask real problems.

efcore-patterns

Entity Framework Core best practices including NoTracking by default, query splitting for navigation collections, migration management, dedicated migration services, and common pitfalls to avoid.

ilspy-decompile

Understand implementation details of .NET code by decompiling assemblies. Use when you want to see how a .NET API works internally, inspect NuGet package source, view framework implementation, or understand compiled .NET binaries.

mailpit-integration

Test email sending locally using Mailpit with .NET Aspire. Captures all outgoing emails without sending them. View rendered HTML, inspect headers, and verify delivery in integration tests.

marketplace-publishing

Workflow for publishing skills and agents to the dotnet-skills Claude Code marketplace. Covers adding new content, updating plugin.json, validation, and release tagging.

Verwandte Skills