What problem does it solve? Setting up observability in .NET applications involves choosing the right NuGet packages, wiring up the OpenTelemetry SDK correctly in Program.cs, and avoiding silent failures like mismatched ActivitySource names. This Skill provides a complete, correct workflow for instrumenting ASP.NET Core apps with distributed tracing, metrics, and correlated logging. ## Core Features & Use Cases - Full SDK Setup: Install the correct OpenTelemetry packages and configure tracing, metrics, and logging with a single OTLP exporter in Program.cs. - Custom Instrumentation: Create custom spans with ActivitySource and custom metrics (counters, histograms, up-down counters) via IMeterFactory for business operations. - Distributed Context Propagation: Manually propagate trace context across message queues and other non-HTTP boundaries. - Use Case: You are adding observability to an order-processing microservice. Use this Skill to instrument HTTP requests automatically, add custom spans for payment and validation steps, record order metrics, and export everything to Jaeger or the Aspire dashboard via OTLP. ## 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.