Monitoring Microservices
summary
Argues monitoring must shift primary key from host to service and adopts RED: rate error duration as the three service metrics, shows dashboards built with Prometheus and Grafana, and demonstrates a platform approach that instruments load‑balancers so teams need not change binaries. Presents Weave Scope (v0.14), an open source Go tool that auto-discovers topology by joining conntrack and /proc data, and demos a ptrace prototype for distributed tracing that works without app changes but is currently too slow for production.
AI-written summary · about
chapters (7)
- 0:00Microservices monitoring intro
- 1:08Traditional monolith monitoring
- 3:58RED method for SLIs
- 7:26Visualizing microservices
- 18:23Distributed tracing
- 28:19Monitoring techniques summary
- 29:21Q&A
related talks
28mMonitoring Microservices w. Prometheus & Tracing Apps w. OpenTracing
24mMonitoring Microservices The Right Way
34mPrometheus: Monitoring Microservice Applications
16mMonitoring Microservices The Right Way
10mMonitoring Microservices: A Challenge
34mMonitor My Socks: Using Prometheus in a Polyglot Open Source Microservices
30mSeeing RED
35mMonitoring Distributed Java Applications at Scale
