Downloaded 58 times
Uploaded byMartin Etmajer
Monitoring Microservices at Scale on OpenShift (OpenShift Commons Briefing #52)
Martin Etmajer discusses using Dynatrace for monitoring microservices on OpenShift, highlighting the complexities and interdependencies of microservices. Key learnings include the necessity to design for failure and recognize the unreliability of networks. The document emphasizes the importance of continuous delivery and performance monitoring, offering key takeaways such as auto discovery and auto problem analysis.
More Related Content
Similar to Monitoring Microservices at Scale on OpenShift (OpenShift Commons Briefing #52)
Monitoring Microservices at Scale on OpenShift (OpenShift Commons Briefing #52)
- 1. Martin Etmajer, TechnologyLead Monitoring Microservices at Scale on OpenShift with Dynatrace
- 2.
- 3. Digital Performance Managementfor Biz, Devs and Ops Modernize Operations Optimize Customer Experience Accelerate Innovation
- 4.
- 5.
- 6.
- 7. Velocity: Independent Developmentand Deployment
- 8.
- 9.
- 11.
- 12. #1: Microservices arecomplex Lower inner vs. higher outer complexity
- 13.
- 16.
- 23. #2: Microservices don‘tfail independently Design for failure
- 25. Your application hasfailed :-( What’s affected? What’s the impact? What’s the root cause?
- 26. Confidential, Dynatrace LLC What’sthe impact? What’s affected? What’s the root cause?
- 28. #3: The networkisn‘t reliable
- 29. Tightly coupled. ReallyDistribute?
- 30.
- 31.
- 32.
- 33. Option 1a: DynatraceOneAgent for Full-Stack Monitoring
- 34. Option 1a: DynatraceOneAgent for Full-Stack Monitoring
- 35. Option 1b: DynatraceOneAgent for Full-Stack Monitoring
- 36. Option 1b: DynatraceOneAgent for Full-Stack Monitoring
- 37. Confidential, Dynatrace LLC dynatrace/oneagentRed Hat Container Certified
- 38. Option 2: DynatraceOneAgent for PaaS Monitoring
- 39. Option 2: DynatraceOneAgent for PaaS Monitoring oc|s2i|Dockerfile
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46. Don’t just optimizefor speed…
- 47. …instead, release fastand with certainty. Identify bad code before it gets checked in. Collect performance metrics from automated tests. Feed back metrics into Jenkins and auto-stop bad builds.
- 48. 3 Key Takeaways:AAA Auto discovery Auto baselining Auto problem analysis
- 49.