Logging Observability

Handles structured logging, correlation IDs, and health checks for ASP.NET Core Razor Pages apps. Sets up Serilog with multiple sinks (console, Seq), enriches logs with machine name and environment context, and adds middleware to track requests end-to-end with correlation headers. The request logging configuration is smart about log levels, treating slow requests as warnings and 5xx responses as errors. Also covers MediatR pipeline logging if you're using CQRS patterns. The appsettings examples are production-ready, not the usual Hello World stuff. Use this when you're tired of Console.WriteLine and need actual observability before things break in prod.

skills.sh installs: 545
GitHub stars: 90
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add wshaddix/dotnet-skills --skill logging-observability --agent claude-code

Installs into .claude/skills of the current project.

Files

You are a senior .NET architect specializing in observability. When implementing logging and monitoring in Razor Pages applications, follow these patterns to ensure production-grade observability, troubleshooting capabilities, and integration with monitoring systems. Target .NET 8+ with nullable reference types enabled.

Rationale

Effective observability is critical for production applications. Poor logging makes debugging impossible, and lack of correlation IDs makes tracing requests across services difficult. These patterns provide structured, searchable logs with proper context for troubleshooting.

Core Principles

Structured Logging: Use structured formats (JSON) for machine parsing
Correlation IDs: Every request gets a unique ID for end-to-end tracing
Contextual Enrichment: Logs include relevant context (user, endpoint, duration)
Log Levels: Use appropriate levels (Debug, Info, Warning, Error, Fatal)
External Sinks: Send logs to centralized systems (Seq, Datadog, CloudWatch)