A Bartender's Guide to Network Monitoring
summary
Claims that SLOs+SLIs drive vendor accountability, that an outside-in DEM approach finds real user pain, and that monitoring must include DNS/BGP, CDN edges and origin. Gives a concrete case where a streaming rollout shows UAE users suffering because the CDN uses a distant PoP; the fix is renegotiating CDN routing and deploying high-frequency object tests from end-user locations to origin. Recommends mapping critical-path journeys and watching multi-dns multi-cdn stacks.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:25The Menu
- 8:09Know your base: What kind of "bar" are you?
- 10:47Know your base: Know your customers
- 14:45Know your base: Case Study
- 20:44The right ingredients: The digital experience
- 24:03The right ingredients: Use Case
- 28:17Beyond the recipe: The tools needed
- 32:07Shaken not stirred
- 34:00Mix and serve neat
related talks
29mSex, Lies & Videotapes: The Truth Behind Your CDN Logs
30mOff the Beaten Path: Moving Observability Focus from Your Service to Your Customer
35mFrom Monitoring to Observability: Left Shift your SLOs with Chaos
57mSLI and SLO for the Business: Monitoring Quality Across 200+ Products
23mNetwork SLOs: Knowing When The Network Is The Barrier To Application Quality Of Experience
46mLessons learned from monitoring a large production network
30mFrom Monitoring to Observability: Left Shift your SLOs with Chaos
22mWhy is it always DNS, TLS, and bad configs?