Microservices monitoring challange
0 likes1,241 views
This document contains notes from a presentation on cloud capacity planning and monitoring challenges. It discusses the importance of capacity and performance management to understand how to safely support customer needs. It notes that cloud systems use the same queue management formulas as traditional systems. The document emphasizes understanding systems at scale through proper monitoring of logs, metrics, alerts and trends. It also stresses that tools alone are not enough and that recovery must be part of the design through practices like blue/green deployments and backups.
Microservices monitoring challange
- 25. 2015 ROBERT BIGOS 2 Know unknowns and unknown unknowns Reports that say that something hasn't happened are always interes2ng to me, because as we know, there are known knowns; there are things we know we know. We also know there are known unknowns; that is to say we know there are some things we do not know. But there are also unknown unknowns -- the ones we don't know we don't know Donald Rumsfeld, February 12th, 2004 DOD News Briefing Source: http://www.defense.gov/transcripts/transcript.aspx?transcriptid=2636
- 29. 2015 ROBERT BIGOS 2 Lessons learned ? suggested approach WHY WHAT HOW most popular HOW HOW HOW . try understand big picture , go deeper , focus on details
- 30. 2015 ROBERT BIGOS 2 Lessons learned ? There is No Single Version of the Truth be open for communicaPon There is NO perfect tools we can build beCer teams and beCer communicate to close feedback loop Cloud scale design , operaPonal design not just easy to consume There is no GO@FASTER opPon in the Cloud
- 31. 2015 ROBERT BIGOS 2 Lessons learned ? Keep standards: date ISO_8601 example Keep what you need not just everything Keep slim: json is nice but Keep informaPon not just numbers/hashtags AutomaPzaPon requires standardisaPon Microservices architecture assume : team = silo/kingdom. Dont use wrong paCerns! If you don't understand your system , your micro service will not work in scale. Avoid: designed by programmers for programmers, keep balance