Message processing failed! But what's the root cause?
summary
Message chains fail because the initiating action, the exact message sequence, or an ordering assumption is wrong — fixable by asserting outgoing messages, adding integration tests that model concurrent out of order delivery, and tracing the transaction across services. Uses OpenTelemetry with W3C trace‑context headers, .NET Activity API and exporters (Jaeger/Azure/collector) to attach trace id to logs, then navigate spans to find the bad mapping; expect memory, latency and storage costs.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:31Autonomous components
- 11:31Rethinking the rule of 3
- 21:39Distributed tracing
- 25:51Observability signals
- 42:45Logging vs tracing
related talks
37mMessage processing failed! But what's the root cause?
58mMessage processing failed! But what's the root cause?
01h 13mMessage Processing Failed! But What’s the Root Cause?
01h 01mMessaging: The fine line between awesome and awful
53mMessaging: The fine line between awesome and awful
32mDisintegrated telemetry: The pains of monitoring asynchronous workflows
13mSparking Joy for Engineers with Observability
31mFrom Alerts to Insights: Performing Trace-Based Causation at Scale