Microservices promise to increase time-to-market, support growth and foster innovation by enforcing Agile, product-centered and self-enabled teams. However, building a system of microservices that actually works is not an easy endeavour - after all, you're building a highly dynamic, distributed and fault-tolerant system. In this presentation I'll share important learnings around microservices and how to use the Dynatrace digital performance management platform on Red Hat's OpenShift to manage the inherent complexities of microservices-oriented architectures.

1. Martin Etmajer, Technology Lead
Monitoring Microservices at Scale
on OpenShift with Dynatrace

2. martin.etmajer@dynatrace.com
@metmajer
Martin Etmajer
Technology Lead

3. Digital Performance Management for Biz, Devs and Ops
Modernize
Operations
Optimize Customer Experience
Accelerate
Innovation

4. Dynatrace ♥ OpenShift

5. Why Microservices?

6. Why Microservices?

7. Velocity: Independent Development and Deployment

8. Growth: Independent Scaling

9. Innovation: Agile teams

11. 3 Microservices Learnings

12. #1: Microservices are complex
Lower inner vs. higher outer complexity

13. Environmental Complexity

16. Inter-service Complexity

23. #2: Microservices don‘t fail independently
Design for failure

25. Your application has failed :-(
What’s affected?
What’s the impact?
What’s the root cause?

26. Confidential, Dynatrace LLC
What’s the impact?
What’s affected?
What’s the root cause?

28. #3: The network isn‘t reliable

29. Tightly coupled. Really Distribute?

30. Confidential, Dynatrace LLC

31. How to Dynatrace?

32. Dynatrace OneAgent

33. Option 1a: Dynatrace OneAgent for Full-Stack Monitoring

34. Option 1a: Dynatrace OneAgent for Full-Stack Monitoring

35. Option 1b: Dynatrace OneAgent for Full-Stack Monitoring

36. Option 1b: Dynatrace OneAgent for Full-Stack Monitoring

37. Confidential, Dynatrace LLC
dynatrace/oneagent Red Hat Container Certified

38. Option 2: Dynatrace OneAgent for PaaS Monitoring

39. Option 2: Dynatrace OneAgent for PaaS Monitoring
oc|s2i|Dockerfile

40. Dynatrace with OpenShift *

41. Additional Resources

42. Additional Resources

43. Dynatrace Free Trial

44. Outlook?

45. Dynatrace Inside
Continuous Delivery

46. Don’t just optimize for speed…

47. …instead, release fast and 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. martin.etmajer@dynatrace.com
@metmajer
Martin Etmajer
Technology Lead
Questions?