What problem does it solve? ASP.NET Core applications without structured logging and observability are difficult to debug in production, making it hard to trace requests across services, diagnose failures, and monitor system health. ## Core Features & Use Cases - Structured Logging with Serilog: Configure bootstrap loggers, JSON-formatted output, contextual enrichment, and external sinks like Seq for centralized log aggregation. - Correlation IDs & Request Tracing: Add middleware that assigns every request a unique correlation ID and enriches logs with user, path, and timing context for end-to-end tracing. - Health Checks & OpenTelemetry: Implement database and external service health checks with JSON responses, plus distributed tracing and metrics via OpenTelemetry instrumentation. - Use Case: When deploying a Razor Pages application to production, use this Skill to set up Serilog with correlation IDs, add health check endpoints for your database and Redis cache, and wire OpenTelemetry tracing so you can diagnose a slow order-processing request across services. ## Quick Start Set up Serilog structured logging with correlation ID middleware and health checks in my ASP.NET Core Razor Pages application.