Monitoring OpenStack? Piece of cake!
Download as PPTX, PDF0 likes136 views
The document discusses the importance of correlation in monitoring OpenStack, highlighting how statistical measures can indicate performance issues in application environments. It emphasizes the relationship between resource capacity, service availability, and user experience. The author, Dirk Wallerstorfer, invites readers to visit the Dynatrace booth for further demonstrations.
Monitoring OpenStack? Piece of cake!
- 1. confidential Monitoring OpenStack? Piece of cake! May 2, 2017 Dirk Wallerstorfer Technology Lead OpenStack
- 3. “Celebrate the power of the individual” “Cloud is all about applications” “Hello, I’m cloud”
- 4. Celebrate the power of the individual
- 5. Cloud is all about applications
- 7. Correlation Correlation is a statistical measure that indicates the extent to which two or more variables fluctuate together.
- 8. Correlation doesn‘t imply causation B Z Host CPU > 90%BookingService response time increases by 2 seconds B X Z C A W D Y
- 12. Resource capacity and utilization OpenStack service availability/performance Supporting services Log files Applications running on top Dependencies Correlation of metrics/events/data Real user monitoring, UX affects $ PaaS
- 13. This is NOT a REGULAR SIZE application environment! B X Z C A W D Y
- 15. Resource capacity and utilization OpenStack service availability/performance Supporting services Log files Applications running on top Dependencies Correlation of metrics/events/data Real user monitoring, UX affects $ PaaS
- 17. Thank you! Stop by the Dynatrace booth #141 for a demo! Dirk Wallerstorfer Technology Lead OpenStack dirk.wallerstorfer@dynatrace.com @wall_dirk
Editor's Notes
- #2: How easy it can be to monitor OpenStack I’m going to use the next 20 minutes I will explain it based on an real-life application
- #3: So, how can you monitor this application?
- #4: Paul Cormier, RedHat No doubt, monitor UX: $, customer satisfaction, that they come back and use your services again No doubt, monitor apps: services/database perf, resource issues, ... No doubt, monitor OpenStack: instances, services, supporting services, log files ... the list goes on. Three-way split, different interest groups: CFO (memory utilzation?), CTO, COO
- #5: information about visits, session, duration of sessions, bounce rates, conversions, ... oh, your bounce increased? well maybe the restructuring of the website wasn’t so good after all ... good, that we know that now! You as a company that provides services need that data, otherwise you’re flying blind. CFO, CEO
- #6: CTO / COO
- #7: monitor, you might have blind spots, customers/users complain! So all of this information needs to be converged in a smart way to not overload you with unnecessary details.
- #8: not only correlation, also causal relation
- #10: Update of the Payment Service of one of the rookie developer that are convinced that you have to write everything on your own and reinvent the wheel on a daily basis.
- #13: Putting it all together now. With large environments, manual introspection and correlation and log browsing won’t cut it anymore ... people don’t scale as well ...
- #18: SEE FOR YOURSELF!