observability-tracing

OpenTelemetry distributed tracing is implemented by configuring Aspire service defaults, registering custom ActivitySources for Wolverine and Marten, and propagating trace contexts across gRPC, Kafka, and Azure Service Bus to achieve end-to-end message flow visibility.

Trace context propagation across Kafka and gRPC requires instrumenting the OpenTelemetry HTTP and gRPC client packages to ensure distributed tracing spans are correctly linked across different service boundaries and message brokers.

Yes, enabling tracing for Wolverine and Marten requires adding OpenTelemetry SDK packages, including Extensions.Hosting, OTLP Exporter, and specific instrumentation libraries for ASP.NET Core, HTTP, and gRPC clients.

The best way to set up custom spans in Aspire is by utilizing AddServiceDefaults() for foundational tracing and defining per-service ActivitySource conventions to capture domain-specific operations within your application.

Yes, you can use Aspire service defaults to add observability to a ride-sharing application by establishing foundational OpenTelemetry tracing for gRPC calls, Kafka messages, and database operations.

Broken distributed traces across message brokers occur when trace context propagation is not explicitly configured for Kafka and Azure Service Bus, requiring correct ActivitySource instrumentation to link spans.