Tracing Node. The Open Source Edition.
summary
A demo app (a taps versus spaces voting page) produces a reproducible memory leak sawtooth from PM2 restarts and the talk shows how to collect response times, event‑loop and GC metrics, heap and CPU and ship them out of process into a statsd → Telegraf → InfluxDB → Grafana pipeline that takes a few hours to set up. Instrumentation requires per‑library hooks for context propagation in Node, and distributed traces land in Zipkin so Zipkin traces identify failing service blue.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:04Metrics Collection Pipeline
- 8:17Memory Usage
- 13:25Microservices
- 15:18Propagate Context
- 19:45Open Tracing
- 20:28Open Sensors
related talks
20mMonitoring, And Visualizing your Node.JS server with Open Source tools
17mLogging, Metrics, and Tracing with Node.js
28mTracing Node. The Open Source Edition
25mNode js applications diagnostics under the hood
57mTroubleshooting Node.js Applications Under the Hood
22mExamining Observability in Node.js
24mArchitect for Scale - My Learnings in Node.js (A case study)
14mExample Debugging Session using DTrace and MDB