AWS Summit - Chicago 2016 - New Relic - Monitoring the Dynamic Cloud
•Download as PPTX, PDF•
1 like•415 views
Lee Atchison gave a presentation on monitoring dynamic cloud environments. He explained that cloud resources are now highly dynamic, with containers starting and stopping within minutes. This requires monitoring not just servers but the entire lifecycle of cloud components. Both operations and development teams are impacted by this change, as cloud architecture is now integral to application design. Traditional monitoring is insufficient - tools are needed that provide full stack visibility across servers, applications, and provisioning in dynamic cloud environments.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to AWS Summit - Chicago 2016 - New Relic - Monitoring the Dynamic Cloud
Similar to AWS Summit - Chicago 2016 - New Relic - Monitoring the Dynamic Cloud (20)
More from Lee Atchison
More from Lee Atchison (9)
Recently uploaded
Recently uploaded (20)
AWS Summit - Chicago 2016 - New Relic - Monitoring the Dynamic Cloud
- 1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Lee Atchison, Principal Cloud Architect and Advocate at New Relic, Inc. April 19, 2016 – Chicago, IL Life’s Too Short… ... for Cloud without Analytics Monitoring the Dynamic Nature of Cloud Computing
- 2. Safe Harbor This document and the information herein (including any information that may be incorporated by reference) is provided for informational purposes only and should not be construed as an offer, commitment, promise or obligation on behalf of New Relic, Inc. (“New Relic”) to sell securities or deliver any product, material, code, functionality, or other feature. Any information provided hereby is proprietary to New Relic and may not be replicated or disclosed without New Relic’s express written permission. Such information may contain forward-looking statements within the meaning of federal securities laws. Any statement that is not a historical fact or refers to expectations, projections, future plans, objectives, estimates, goals, or other characterizations of future events is a forward-looking statement. These forward-looking statements can often be identified as such because the context of the statement will include words such as “believes,” “anticipates,”, “expects” or words of similar import. Actual results may differ materially from those expressed in these forward-looking statements, which speak only as of the date hereof, and are subject to change at any time without notice. Existing and prospective investors, customers and other third parties transacting business with New Relic are cautioned not to place undue reliance on this forward-looking information. The achievement or success of the matters covered by such forward-looking statements are based on New Relic’s current assumptions, expectations, and beliefs and are subject to substantial risks, uncertainties, assumptions, and changes in circumstances that may cause the actual results, performance, or achievements to differ materially from those expressed or implied in any forward-looking statement. Further information on factors that could affect such forward-looking statements is included in the filings we make with the SEC from time to time. Copies of these documents may be obtained by visiting New Relic’s Investor Relations website at http://ir.newrelic.com or the SEC’s website at www.sec.gov. New Relic assumes no obligation and does not intend to update these forward-looking statements, except as required by law. New Relic makes no warranties, expressed or implied, in this document or otherwise, with respect to the information provided.
- 3. Who am I? Specialize in: Cloud computing Services & Microservices Scalability, Availability 28 years in industry 7 in Amazon Retail & AWS (Built SW/VG AppStore, AWS Elastic Beanstalk) 4 in New Relic (Architecture Lead, Cloud, Service Migration) @leeatchison leeatchison
- 4. We want better apps faster Dynamic Environment Better Data Center How do we use the cloud to accomplish this?
- 5. Cloud as a Dynamic Tool
- 6. Cloud as a “Dynamic Tool for Dynamic Apps” Use only the resources you need
- 7. Cloud as a “Dynamic Tool for Dynamic Apps” Use only the resources you need Allocate / de-allocate resources on the fly
- 8. Cloud as a “Dynamic Tool for Dynamic Apps” Use only the resources you need Resource allocation is an integral part of your application architecture Allocate / de-allocate resources on the fly
- 9. Dynamic Cloud Resources are: Application is aware of and is controlling traditional OPs resources De-allocatedConsumedAllocated Auto Scale
- 10. Dynamic Cloud Docker containers: • Quicker / cheaper startup / shutdown even than EC2 instances • Easy to consume Docker containers much like you do “processes” • Perform jobs: – In a script – Off of some queue of job requests Docker is making the cloud even more dynamic
- 11. Dynamic Cloud 100 10K 1M 3.7 M 83 days 333 days Docker Container Age (Count vs. Hours)
- 12. Dynamic Cloud 950,000 11% under one minute Docker Container Age (by Minute Under and Hour)
- 13. Dynamic Cloud Technologies EC2/Spot Instances Load balancing Auto Scaling Queues and notifications Docker Dynamic Cloud is about scaling
- 14. How do I monitor the Dynamic Cloud? Dynamic Cloud has unique monitoring requirements…
- 15. Responsibility (Dynamic Cloud) Server OS Server (Virtual) Hardware Application & Application Microservices Application & Application Microservices Application & Application Microservices Provisioning • Multiple Applications & Application Microservices & Dynamic services • Servers & Virtual Hardware & Infrastructure
- 16. AWS Infrastructure Server OS Server (Virtual) Hardware CloudWatch AWS CONSOLE DASHBOARDS Application & Application Microservices Application & Application Microservices Application & Application Microservices Provisioning
- 17. AWS Infrastructure New Relic work together Server OS Server (Virtual) Hardware CloudWatch AWS CONSOLE DASHBOARDS Application & Application Microservices Application & Application Microservices Application & Application Microservices Provisioning
- 18. AWS Infrastructure New Relic work together Server OS Server (Virtual) Hardware CloudWatch AWS CONSOLE DASHBOARDS Application & Application Microservices Application & Application Microservices Application & Application Microservices Provisioning CloudWatch & AWS monitoring New Relic monitors
- 19. How do you monitor this? Server OS Server (Virtual) Hardware Application & Application Microservices Application & Application Microservices Application & Application Microservices Provisioning ? How do you monitor this?
- 20. Where did it go? It was just here!!! ? The thing you monitored 10 minutes ago… ...doesn’t exist anymore!
- 21. Dynamic Cloud 950,000 11% under one minute Docker Container Age (by Minute Under and Hour)
- 22. Monitoring the Dynamic Cloud Very different than monitoring traditional Data Center components Monitor the Cloud Components themselves Monitor the lifecycle of the Cloud Components
- 23. Who is impacted by Dynamic Cloud? Better Data Center Can I scale my server fleet? Can apps run anywhere? How do they perform in the cloud? Operations Data center is a data center… Development Dynamic Cloud
- 24. Who is impacted by Dynamic Cloud? Better Data Center Can I scale my server fleet? Can apps run anywhere? How do they perform in the cloud? Operations Data center is a data center… Development Dynamic Cloud What is a container? Why do I care?? It was just here, where did it go???
- 25. Who is impacted by Dynamic Cloud? Better Data Center Can I scale my server fleet? Can apps run anywhere? How do they perform in the cloud? Operations Data center is a data center… Development Dynamic Cloud What is a container? Why do I care?? It was just here, where did it go??? Cloud architecture is integral to the application architecture Developers deeply involved in cloud activities
- 26. Change is speeding up Traditional Data Center Cloud Data Center Dynamic Cloud Dynamic Cloud enables better applications faster. Good Better Best The way you’ve done things in the past won’t work in the future.
- 27. Dynamic Cloud EC2 Server running application / processes Docker container Process running a command Things happen faster because of… This is hard
- 28. Dynamic Cloud EC2 Server running application / processes Docker container Process running a command Lambda Function performing a task or operation Things happen faster with…
- 29. Change is speeding up Traditional Data Center Cloud Data Center Dynamic Cloud Dynamic Cloud enables better applications faster. The rate of change is increasing… Good Better Best The way you’ve done things in the past won’t work in the future.
- 30. Monitoring just the server EC2 Instance Application & Application Microservices Server OS Server (Virtual) Hardware CloudWatch AWS CONSOLE Worked when rate of change was low…
- 31. Monitoring just the server Server OS Server (Virtual) Hardware Application & Application Microservices Application & Application Microservices Application & Application Microservices Provisioning Insufficient in the cloud: • Rate of change is faster • Problems come up quicker • “Server” isn’t a server anymore • “Provisioning” isn’t provisioning anymore You need top to bottom monitoring… You need full stack accountability...
- 32. You Need A Solid Monitoring Partner... Customers Mobile / Apps / Browser On-Premises On Premises Relational Data EC2 AWS Container Service AWS RDSSynthetic Customers S3 NoSQL AWS Storage Services Your Responsibilities • Application code & 3rd party services • App architecture • Customer experience • On-Premises components AWS Responsibility: • Service Availability & Performance • Provisioning & operation of DC • Isolation & security of resources • Service maintenance & innovation NoSQL
- 33. Want to Learn More? Monitoring the Hybrid Cloud How do you measure and make decisions across on-premises data centers, dynamic clouds, and hybrid clouds? Registration: http://bit.ly/NR421 Webinar: April 21 @ 8 AM PT
- 34. Want to Learn More?
- 35. Thank You! Lee Atchison, Principal Cloud Architect and Advocate at New Relic, Inc. Architecting for Scale Published by: O’Reilly Media, Available: June 2016 www.architectingforscale.com @leeatchison leeatchison
Editor's Notes
- >>> Hello, my name is xxx and this is Monitoring the Dynamic Nature of the Cloud…
- I work for New Relic. New Relic is a public company. Nothing I say should that appears to be a “forward-looking statement” should be assumed accurate. Nothing I say should be considered financial advice. I’m not a lawyer, I’m not a financial analyst.
- Why are we here? We’re here because people want better apps, faster. There are two ways to use the cloud to accomplish this: Better Data Center: You need additional capacity, or easier to acquire capacity Dynamic Environment: You need the unique dynamic qualities of the cloud
- As a ”Dynamic Tool” the cloud allows you to: **** Use only the resources you need, only when you need them Allocate and deallocate resources ON THE FLY This allocation process becomes an integral part of your application architecture
- As a ”Dynamic Tool” the cloud allows you to: Use only the resources you need, only when you need them **** Allocate and deallocate resources ON THE FLY This allocation process becomes an integral part of your application architecture
- As a ”Dynamic Tool” the cloud allows you to: Use only the resources you need, only when you need them Allocate and deallocate resources ON THE FLY **** This allocation process becomes an integral part of your application architecture
- >>> Because of this rapid allocation/deallocation: >>> Your application is aware of and is controlling TRADITIONAL Ops RESOURCES Involving scaling Load balancing >>> Technologies used in the cloud help speed up new application deployment…
- >>> Take Docker, for example >>> While not a “cloud technology”, it is certainly used heavily in the dynamic cloud: * Docker makes it even quicker and cheaper to start/stop services and application components * You can consume a docker container much like you do a traditional “process”…that light weight * Individual containers can perform jobs in a script or off of a job queue of some sort
- This chart shows lifespan of traditional docker containers that New Relic has been monitoring. It clearly shows that: * Docker is useful both for long running application and service needs… * Docker allows very dynamic “quick start/finish” type jobs as well -> If we look at that shortest term data point on the far left, and expand it...
- You see that over 11% of all docker containers we examined run UNDER ONE MINUTE in duration… Clearly, Docker usage fits very well into the dynamic usage of the cloud.
- >>> Besides Docker, there are many technologies in the cloud that enable this dynamic usage: Auto Scaling – spin up instances easy Spot Instances – cheaply use spare capacity dynamically Queues & Notifications Dynamic load balancing
- Given this dynamic nature of the cloud, this creates some unique monitoring requirements.
- >>> Here is your application and services running in a dynamic cloud. Multiple Applications Multiple Services Dynamic Services >>> When things change here, then what? * What happens if new components are created/destroyed? * What visibility do you have into the changing nature of these components? * How do you detect problems when they break? How do you find optimizations?
- >>> You still need to use the cloud infrastructure to monitor your infrastructure: * Server virtualizations * Provisioning process * Networking, Queues * Other PaaS/SaaS applications
- >>> And tie this into traditional Application Performance Monitoring
- >>> Together, they are both needed to give you the visibility you need into: * How your code is working * How your devices are provisioned * How your infrastructure components are working >>> All of this is still important…but...
- >>> How do you monitor this? >>> Resources are allocated and deallocated quickly…
- >>> With resources coming and going… >>> ... The thing you monitored 10 minutes ago...doesn’t even exist anymore!
- >>> Remember the docker data? These are entire Linux stacks that come and go in less than 60 seconds!!!
- >>> This whole process is very different than monitoring a traditional data center… The Dynamic cloud has different monitoring requirements >>> You must: >>> * First monitor the cloud components themselves… This is your application, services, servers, and the like >>> * Second monitor the lifecycle of the cloud components When are components created and added to your system? When are they removed? How do the constantly moving components interact? What if that interaction fails? >>> This is very different than a traditional data center...
- >>> And who is impacted by this changing environment?
- And who is impacted and the problems involved change as well… **** Operations? certainly add new questions: * What is a container? Why do I care? * It was here a moment ago, where did it go? Development? now cares a great deal:
- And who is impacted and the problems involved change as well… Operations? certainly add new questions: **** Development? now cares a great deal: * The specific cloud architecture is integral to the application architecture * Developers are deeply involved in the selection, integration, and use of the specific cloud resources
- >>> It use to be that monitoring “Just the Server” was enough, but not any more >>> With the cloud: * Apps are created faster * Apps change faster * Infrastructure changes even faster
- >>> In the dynamic cloud, the size and shape of our resources is changing… >>> Technology is breaking our fundamental assumptions about how our infrastructure works >>> THIS IS HARD…
- >>> And it’s about to get harder… >>> Technologies like Lambda are reshaping all of our assumptions on how things are suppose to work... >>> ***And don’t think it’s too far in the future...your engineers are thinking of using it NOW!!!
- >>> Clearly, typical server monitoring is not sufficient… >>> Change is happening faster... >>> When you use the cloud, your apps change faster…
- >>> When the rate of change was low >>> low level server monitoring was sufficient.
- >>> This is now insufficient * Rate of change is faster * Problems come up quicker… >>> ”Server” isn’t a server anymore and >>> “Provisioning” isn’t provisioning anymore >>> You need top to bottom monitoring, with full stack accountability.
- >>> You need a solid monitoring partner Like New Relic