Operational and Business Insights from Tracing Distributed Microservices
summary
Shows a working OpenShift demo using Hawkular APM as an OpenTracing-compliant tracer, a Vert.x microservice set, and a load script that generates orders. Captures spans named place order and derives business metrics (43% failures due to "item not found") from trace aggregations. Uses trace context propagation across services, inspects individual traces, and runs a canary with 20% traffic to compare versions before scaling; instrumentation adds measurable but controllable overhead.
AI-written summary · about
chapters (16)
- 0:00Distributed tracing intro
- 2:15Tracing code execution
- 4:45Tracing in microservices
- 6:32OpenTracing and HawtIO APM
- 7:16Demo goals and business insights
- 9:06Java tracing walkthrough
- 11:23Demo environment setup
- 12:29Tracing order placement
- 15:44Spans in HawtIO APM
- 17:39Business insights from traces
- 19:05Operational insights with canary
- 20:32Canary release deployment
- 22:45Performance comparison
- 24:06Scaling and retiring versions
- 26:06Summary and OpenTracing resources
- 27:14Q&A on tracing overhead
related talks
22mMonitoring Microservices applications on OpenShift
24mDistributed Tracing : New DevOps Foundation.
28mMonitoring Microservices w. Prometheus & Tracing Apps w. OpenTracing
31mUnderstanding Microservices with Distributed Tracing
35mNavigating the Distributed Systems Execution Maze With OpenTracing
42mDistributed Monitoring: How to understand the Chaos
47mUsing metric and traces to diagnose our cloud-native applications
52mPerfecting reliable code delivery for the cloud
