With Amazon EKS, AWS Fargate, and Amazon ECS, AWS makes it easy to run containerized applications. However, a perfectly running containerized environment does not ensure a perfect user experience for your customers. In this session, we explore the interdependencies between container environment and the health of containers and applications. We examine how container health can jeopardize application health and how to identify noisy neighbors that might slow down your application’s response time and impact the user’s experience. We show you how to get full insight into your container environment, containers, and applications without touching a single line of application code. This presentation is brought to you by AWS partner, Dynatrace.

1. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Unified Monitoring of the Container
Environment, Containers, and
Applications
Asad Ali
Sr. Director, Center of Excellence
Dynatrace LLC
@AsadThoughts
D E M 0 9 - S R

2. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Agenda
• Different layers of monitoring
• Importance of service
monitoring
• Impact of common microservice
patterns on performance

3. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Container health != service health != application health
Container health
Microservices health
Application health
IaaS health

4. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Container health != service health != application health
Container health
Microservices health
Application health
IaaS healthIaaS health

5. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Container health != service health != application health
Container health
Microservices health
Application health
IaaS health
container statscontainer stats

6. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Container health != service health != application health
Container health
Microservices health
Application health
IaaS health

7. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Container health != service health != application health
Container health
Microservices health
Application health
IaaS health

8. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Highly dynamic and distributed environments

9. S U M M I T © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.

10. S U M M I T © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.

11. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Deployment dependencies vs. microservice dependencies

12. S U M M I T © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.

13. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
WPO (Web Performance
Optimization) taught us optimizing
resource dependencies when loading
a web page by analyzing Resource
Waterfalls

14. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Especially useful when page loads get
very complex and overloaded:
3rd party dependencies, non-
optimized resources, wrong cache
settings, loading too much data too
early…

15. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
SFPO (Service Flow & Performance
Optimization) teaches us how to
optimize (micro)service dependencies
through Service Flows

16. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Especially useful to identify: inefficient 3rd party services,
recursive call chains, N+1 Query Patterns, loading too
much data, no data caching…
-> sounds very familiar to WPO

17. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Understanding where time within a
service and between service calls is
spent

18. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Classical cascading effect of
recursive service calls!

19. S U M M I T © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.

20. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Tightly coupled. Really distributed?

21. S U M M I T © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.

22. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Dynatrace OperatorDynatrace Operator

23. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Automatic DiscoveryAutomatic Dependency Map

24. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Thank you!
S U M M I T © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Asad Ali
Sr. Director, Center of Excellence
Dynatrace LLC
@AsadThoughts