What problem does it solve? Setting up observability in ASP.NET Core involves choosing the right NuGet packages, wiring up the OpenTelemetry SDK correctly, and avoiding silent failures like unmatched ActivitySource names. This Skill provides a complete, validated workflow for instrumenting .NET applications with distributed tracing, metrics, and correlated logging. ## Core Features & Use Cases - Full SDK Setup: Installs the correct OpenTelemetry packages and configures tracing, metrics, and logging in Program.cs with a single OTLP exporter. - Custom Telemetry: Creates custom spans with ActivitySource and custom metrics (Counter, Histogram, UpDownCounter) via IMeterFactory for business operations. - Distributed Context Propagation: Handles manual trace context propagation across message queues and non-HTTP scenarios. - Use Case: You are adding observability to an order-processing microservice. Use this Skill to instrument HTTP requests automatically, create custom spans for payment and validation steps, export everything to Jaeger via OTLP, and correlate logs with traces. ## Quick Start Configure OpenTelemetry tracing, metrics, and logging with an OTLP exporter in my ASP.NET Core project and add a custom ActivitySource for my order processing code.