about reinventing the wheel
summary
First Node.js service embeds monitoring and it causes pain: an error-report push loops and kills the service, so move ops out of the app. Use Prometheus scraping for metrics with histograms not averages, send errors as pushes to a collector (avoid recursive retries), store secrets in Vault for secrets instead of code or env, run supervision with monit + runit not in-process restarts, and carry a correlation ID through logs so traces across services actually work.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:54Error logs
- 9:16Logging
- 18:20Service Discovery
- 21:10Process Supervision
- 27:11Lessons learned
related talks
35mMonitoring Microservices
17mRunning Node.js in Production
19mRunning Node.js in Production
26mObserving Node.js: Using Metrics to Improve your Application Performance
26mMonitoring Node.js Microservices on CloudFoundry with Open Source Tools and a Shoestring Budget
17mLogging, Metrics, and Tracing with Node.js
32mDeployment Nirvana
06mMonitoring as a First Step to a New Service