Message Processing Failed! But What’s the Root Cause?
summary
Teams model message flows, add integration tests that assert outgoing messages, and instrument with OpenTelemetry ActivitySource to trace business transactions across queues and services. Implementation uses .NET System.Diagnostics Activity (auto‑instrument HTTP/SQL/Service Bus), exports to tools like Application Insights or Jaeger, and propagates context via the w3c traceparent header. Example fixes include changing inventory logic to reserve stock on order charged and using tail or head sampling to limit overhead; observability works but adds memory, latency, and storage costs.
AI-written summary · about
chapters (16)
- 0:00Debugging distributed systems
- 6:42Debugging message-based systems
- 12:23Testing distributed systems
- 14:51Out-of-order messages
- 17:20Modeling business scenarios
- 22:58Debugging production failures
- 25:29Distributed tracing fundamentals
- 30:53OpenTelemetry framework
- 36:56Tracing in .NET
- 41:51What to trace
- 44:21Tracing code walkthrough
- 51:30Tracing vs logging
- 54:43Metrics introduction
- 57:10Observability costs
- 1:02:46Distributed call stack
- 1:05:15Q&A
related talks
58mMessage processing failed! But what's the root cause?
37mMessage processing failed! But what's the root cause?
55mMessage processing failed! But what's the root cause?
32mDisintegrated telemetry: The pains of monitoring asynchronous workflows
41mDistributed Tracing in .NET
57mYour Distributed System is Talking to You: OpenTelemetry
51mOpenTelemetry tracing for .NET developers
01h 02mAdding Observability to Distributed Systems