Franken Monitoring
summary
Claim: stitching many monitoring products into one system—Franken monitoring—fails to deliver uptime. Concrete problems are cost of evaluation, lack of correlated context causing false alerts, and slow time to resolution. Example: a 500 error alert forces hopping between loggly, data dog and aw2 for diagnosis, costing two minutes which Gartner prices as $111,000. The end result is a temperamental, hard to use mess that does not work.
AI-written summary · about
chapters (4)
related talks
52mHolistic Monitoring
27mBuilding a Scalable Monitoring System
23mMastering Monitoring & Alerting: Key to Seamless Performance
39mThe Many Ways Your Monitoring Is Lying to You
15mAnti-patterns in Security Monitoring
16mMonitoring your platform from multiple locations
42mMonitoring software sucks
31mWe Monitor Everything… Except What Matters