Recommended
Recommended
More Related Content
What's hot
What's hot (15)
Similar to The Synthetic Monitoring Maturity Model
Similar to The Synthetic Monitoring Maturity Model (20)
Recently uploaded
Recently uploaded (20)
The Synthetic Monitoring Maturity Model
- 1. 11 The Synthetic Monitoring Maturity Model David Corrales ThoughtWorks Quito
- 2. A little bit about me @devidcillo ❏ Quality Advocate ❏ 4 years at ThoughtWorks Quito ❏ 3.5 years cross-roleing as Dev and QA ❏ Worked in teams across transportation, investment banking, healthcare and online privacy domains ❏ Participated in and driven various testing and quality-minded initiatives at ThoughtWorks and client sites
- 3. Agenda ❏ A Dark and Stormy Project ❏ What is Synthetic Monitoring? ❏ Why should I spend time on it? ❏ How would I go about it? ❏ Closing
- 4. A Dark and Stormy Project
- 5. Face to Face (React) Online (Php) Specialized (TypeScript) CrowdFunding (Php) Mobile (Swift + Kotlin) AR Project (Swift + Kotlin)
- 6. Face to Face (React) Online (Php) Specialized (TypeScript) CrowdFunding (Php) Mobile (Swift + Kotlin) Monolith (Symfony)
- 7. Face to Face (React) Online (Php) Specialized (TypeScript) CrowdFunding (Php) Mobile (Swift + Kotlin) Monolith(Symfony)
- 9. 9 To Sum Up ❏ Pain points in production deployments ❏ We have flaky outside dependencies ❏ User: “Thing’s broken again!” ❏ Team: “ Why do you want to mess with production?” ❏ Client: “What do I gain by doing this?” ❏ Team: “We can do it, but how?”
- 10. 10 Have you all heard about Synthetic Monitoring?
- 12. A bit of context https://danashby.co.uk/2016/10/19/continuous-testing-in-devops/
- 13. What does this graph tell you? % of failed transactions
- 14. What is synthetic monitoring? Automated tests whose sole purpose is monitoring your app’s health in its production environment
- 16. 16 Why though?
- 17. Your Staging environment is lying to You 17 Marcel Gehlen & Benjamin Hofmann The Final Frontier? Testing in Production TestBash Manchester 2018 Database Issues Real Users Infrastructure Differences
- 18. When a bug is found during development 18
- 20. 20 Wouldn’t it be great if we knew right away if something broke?
- 21. 21 How though?
- 22. 22 Quick refresher ❏ Pain points in production deployments ❏ We have various outside dependencies ❏ User: “Thing’s broken again!” ❏ Team: “ Why do you want to mess with production?” ❏ Client: “What do I gain by doing this?” ❏ Team: “We can do it, but how?”
- 23. 23 First steps ❏ Pain points in production deployments ❏ We have various outside dependencies ❏ User: “Thing’s broken again!” ❏ Team: “ Why do you want to mess with production?” ❏ Client: “What do I gain by doing this?” ❏ Team: “We can do it, but how?”
- 24. 24 Going to Prod is painful... Visualize our discoveries Autonomy Issue responseIncident planning
- 25. 25 Narrowing our focus ❏ Pain points in production deployments ❏ We have various outside dependencies ❏ User: “Thing’s broken again!” ❏ Team: “ Why do you want to mess with production?” ❏ Client: “What do I gain by doing this?” ❏ Team: “We can do it, but how?”
- 26. 26 Third party woes An Objective Identify essential flows Automated TestsLogging Strategy Buy-in Autonomy
- 27. 27 ... ❏ Pain points in production deployments ❏ We have various outside dependencies ❏ User: “Thing’s broken again!” ❏ Team: “ Why do you want to mess with production?” ❏ Client: “What do I gain by doing this?” ❏ Team: “We can do it, but how?”
- 28. 28 Oops... Testing in ProdOpportunity discovery
- 29. 29 Spreading the joy ❏ Pain points in production deployments ❏ We have various outside dependencies ❏ User: “Thing’s broken again!” ❏ Team: “ Why do you want to mess with production?” ❏ Client: “What do I gain by doing this?” ❏ Team: “We can do it, but how?”
- 30. 30 Spreading the joy Risk analysis Visualize our discoveries Buy-in
- 31. 31 Spreading the joy? ❏ Pain points in production deployments ❏ We have various outside dependencies ❏ User: “Thing’s broken again!” ❏ Team: “ Why do you want to mess with production?” ❏ Client: “What do I gain by doing this?” ❏ Team: “We can do it, but how?”
- 32. 32 Spreading the joy! Risk response planning Self healing Opportunity discovery Visualize our discoveries
- 33. 33 Wait, wait, wait...I think we got something here
- 34. 34
- 35. Visualize our discoveriesAutonomy First things first
- 36. Issue response An Objective Identify essential flows Incident planning Automated Tests Logging Strategy Buy-in Risk response planning Testing in Prod Risk analysis Opportunity discovery Self healing Maturity Model v1.0 Reactive Proactive
- 37. 37 Spreading the joy ❏ Pain points in production deployments ❏ We have various outside dependencies ❏ User: “Thing’s broken again!” ❏ Team: “ Why do you want to mess with production?” ❏ Client: “What do I gain by doing this?” ❏ Team: “We can do it, but how?”
- 38. Create your own trail Complete Levels Reactivity to Proactivity (Recommended) Pick your own adventure
- 39. Tools Log-based monitoring Interaction-based monitoring
- 40. Tools Visualizing and Alerts Testing
- 41. How does it look? Monday Tuesday Wednesday FridayThursday Dependency X Dependency Y ThresholdService Effectivity
- 42. How does it look?
- 43. How does it look?
- 44. 44 But what did we learn?
- 45. 45 Yeah, pre-production is lying to us... Let’s do something about it!
- 46. In Closing None of this is magic
- 47. Where would you start if you want to apply Synthetic Monitoring?
- 48. Gracias 🇨🇴 Fanny Barco @FannyBarco fbarco@thoughtworks.com 🇨🇺 Michaell Gonzalez mgonzale@thoughtworks.com 🇨🇺 Adis Rodriguez @adisleydisrodri
- 49. Further Reading ● https://martinfowler.com/bliki/SyntheticMonitoring.html ● https://www.honeycomb.io/resources/white-papers/ ● https://martinfowler.com/articles/qa-in-production.html ● https://testingindevops.org/ ● https://danashby.co.uk/2016/10/19/continuous-testing-in-devops/ ● https://www.practicalmonitoring.com/
- 50. David Corrales Quality Driven Developer dcorrales@thoughtworks.com | @devidcillo | thoughtworks.com 50 Thanks! 😸