Unlocking Observability with React & Node.js
summary
Argues for a concrete full‑stack observability setup that wires React front end to Node.js back end using traceparent ID propagation and session/correlation IDs, visualized in a unified dashboard (Datadog, Jaeger/Zipkin, OpenTelemetry, Elastic, Grafana examples). Describes a 3:00am incident where siloed dashboards delay RCA, a Black Friday compliance microservice that caused cart failures, and a customer that generated 1 million calls in 7 days; claims this approach reduces MTTR, surfaces caching and gateway bottlenecks, and enables anomaly detection and AI‑assisted root cause tagging.
AI-written summary · about
chapters (10)
- 0:00Introduction and Speaker Background
- 0:47Agenda Overview
- 1:06Challenges in Observability
- 3:05Unified Full Stack Observability
- 4:20Implementing Full Stack Observability
- 7:56Key Performance Indicators
- 9:30Distributed Tracing
- 11:30Case Studies and Real-World Scenarios
- 15:35Best Practices and Recommendations
- 18:36Conclusion and Final Thoughts
related talks
17mUnlocking Observability with React & Node.js
43mObservability for React applications
17mObservability in frontend: React Open Telemetry
07mWhy React is Eating the World
17mLogging, Metrics, and Tracing with Node.js
08mComprehensive Observability via Distributed Tracing on Node.js8
08mTrack Slowdowns and Crashes in your React apps
29mExamining Observability in Node.js