Troubleshooting Distributed Workloads ...
summary
Claim: shifting left with dynamic observability cuts MTTR from weeks to minutes to few hours. Shows a Java app instrumented with a dynamic instrumentation agent attached to remote AWS and Oracle deployments, using virtual breakpoints (snapshots), conditional logs and runtime metrics to inspect live executions without redeploys. Integrates with Prometheus and APMs, targets Kubernetes, serverless, CI pipelines, CVE prioritization and feature‑flagged flows, and the demo works as shown.
AI-written summary · about
chapters (9)
- 0:00Troubleshooting distributed workloads
- 4:43Current troubleshooting pain points
- 7:16Key challenges in troubleshooting
- 14:25Why code bugs take longest
- 17:37Debugging Kubernetes & serverless
- 21:55Troubleshooting feature flags & legacy
- 27:17Shifting left observability
- 30:07Live demo: developer observability
- 45:08Q&A
related talks
56mFull-stack observability and application monitoring with
52mPerfecting reliable code delivery for the cloud
25mSpend more time innovating, less time troubleshooting
56mBest practices for optimizing Kubernetes applications on AWS
42mDistributed Monitoring: How to understand the Chaos
13mLightning Talk: Observability-First DevSecOps: Building Resilient Multi-Cloud P...
20mSuper vision smart goggles
37mAutomatically Detect the Top Performance & Scalability Issues in Distributed
