otel-dotnet

Missing OpenTelemetry spans in ASP.NET Core are fixed by correcting SDK instrumentation and propagation configuration in your service setup. This diagnoses trace, metric, and log export issues, ensuring signals reliably reach your backend with proper resource attributes.

Configuring OpenTelemetry trace propagation for async messaging in .NET requires using span Links instead of parent-child relationships for Kafka, RabbitMQ, or Service Bus. This applies correct messaging semantic conventions, ensuring distributed traces connect properly across asynchronous boundaries.

Yes, OpenTelemetry .NET instrumentation works with Azure Functions, gRPC, Minimal APIs, and Worker Services. It supports configuring traces, metrics, and logs across these C# and F# environments, allowing you to set up telemetry from scratch or debug existing missing signals.

The safest way to add OpenTelemetry resource attributes is using a mutation-gate workflow that proposes code diffs first. This waits for explicit user confirmation before applying any changes to your .NET codebase, preventing unintended modifications to your telemetry setup.

OpenTelemetry logs and metrics fail to export correctly from .NET Worker Services due to incorrect OTLP exporter configuration or missing SDK instrumentation. Troubleshooting involves repairing the setup in Program.cs and verifying signals arrive using post-deploy smoke testing.