Cloud Adoption Best Practices with New Relic
Download as PPTX, PDF1 like407 views
The document discusses best practices for cloud adoption, including instrumenting applications early in the migration process to save time and costs. It outlines New Relic products that can be used at different stages of a cloud migration to establish performance baselines, validate improvements, refactor applications, and optimize customer experience. Monitoring with New Relic and Amazon CloudWatch together provides visibility into both application and infrastructure metrics.
Cloud Adoption Best Practices with New Relic
- 1. ©2008–18 New Relic, Inc. All rights reserved Cloud Adoption Best Practices Boris Gouchev Senior Solutions Consultant New Relic
- 2. ©2008–18 New Relic, Inc. All rights reserved 2 Safe Harbor This presentation 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 New Relic makes with the SEC from time to time. Copies of these documents may be obtained by visiting New Relic’s Investor Relations website at 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 presentation or otherwise, with respect to the information provided.
- 3. ©2008–18 New Relic, Inc. All rights reserved New Relic is the Catalyst to Adopt AWS Faster 3 NEWR NYSE – 2014 17k+ Customers 2B Scale: Events & Metrics per Minute 13,500+ Disruptors2,000+ Global Enterprises ~45% App Instances Reporting from AWS
- 4. Confidential ©2008–17 New Relic, Inc. All rights reserved Instrumentation should begin in discovery Where it’s usually added Where monitoring is (mistakenly) recommended today Plan Migrate Run A common tale...
- 5. ©2008–18 New Relic, Inc. All rights reserved 5 Across Our Market, We See Early Instrumentation Saves 16% Per Migration via a 50% Reduction In Acceptance Testing Time 48 hours of instrumentation can save 3 months in work effort and overlap costs *On average for ~750 VMs in a 9 month migration Data Center Decommissioning: 25% Faster Accelerate Time to “Run” Phase: 8% Lower AWS spend Engineering Cost: 21% Less FTE time+ + = $5M Opportunity on a $31M Migration*
- 6. ©2008–18 New Relic, Inc. All rights reserved 6 Cloud Adoption Solution Guide Overview Migrate Run Validate that cloud service use is successful Compare on-prem performance to cloud performance Detect errors or possible issues Establish baseline and validate existing performance Understand impact of application migration Verify and ensure that application is ready for cloud Monitor, query, and alert on application and use of cloud services Understand and optimize cloud spend Re-architect or refactor a cloud application Improve end-user experience for cloud application Identify Issues & Roadblocks Validate Cloud Improvements Acceptance Testing Monitor Cloud Services Application Refactoring Optimize Customer’s Experience Prioritize Migration Order Application Baseline Identify Application Dependencies & Inventory Cloud Spend Optimization KPIs Performance, Capacity, Compute, Availability KPIs Application Error Rates and Response Times, % of Migrated Infrastructure and Apps KPIs Compute Consumption, End-user QoS, Instance and Herd Health Plan
- 7. ©2008–18 New Relic, Inc. All rights reserved 7 Application Baselining Plan InsightsI B Browser M SyntheticsMobile S A InfrastructureAPM I Possible products based on architecture review recommendations Purpose Establish a baseline by monitoring your systems as a black box for performance and availability. A baseline is a measurement of the current performance and availability of your application to use as a starting point. This baseline will be used as a comparison after the migration. Steps 1. Work with the customer and or partner to identify the application or applications that are in scope for a migration 2. Determine the level of instrumentation that will be available for each target application (Can you deploy an agent or not?) 3. Deploy or configure the products to monitor based on level of instrumentation 4. Develop application KPI model and gather metrics 5. Define a Dashboard that contains widgets to show current state Outcome 1. Insights Dashboard showing current state KPIs for each product recommended 2. Additional: set cloud based targets based on on-prem baselines KPIs Availability percentage, Average Duration, Page Load Time, Throughput, Web transaction time, CPU percentage, Average Load, Memory Used Percentage, Response Time, Apdex
- 8. ©2008–18 New Relic, Inc. All rights reserved 8 Migrate Purpose Detail improvements that can be measured as a result of integrating cloud services during the migration. Steps Pre-change: Determine metrics that can be captured that can be baselined. Ideally, these metrics are something that can be measured after the migration. Examples: number of deploys or number of new applications delivered over a given time. These metrics may need to be manually captured. Post change: Define a Dashboard that contains widgets for each metric that has been identified. Outcome Insights Dashboard that includes widgets detailing various improvements over time. The goal is to be able to show improvements over time. Some examples would be improving metrics like Apdex scores, response time, or cloud spend corresponding to the use of advanced cloud services (auto scale up/down, Lambda/functions, etc.). KPIs Apdex, duration, transaction time, cloud spend, HTTP response time and errors Possible products based on architecture review recommendations Validate Cloud Improvements InsightsI B Browser M SyntheticsMobile S A InfrastructureAPM I
- 9. ©2008–18 New Relic, Inc. All rights reserved 9 Run Purpose Re-architecting or refactoring a application in the cloud to achieve better performance, availability, or costs. This should be done within a development environment if possible so as to not affect production. Steps 1. If not already done, deploy and configure products as needed based on architecture review recommendations 2. If available, use deployment markers 3. Establish current migrated application baseline – see Application Baselining 4. Re-architect, refactor, redesign, uncouple, or rewrite application 5. Create a Dashboard to monitor KPIs, keeping close watch on out of baseline metrics or an increase in errors 6. Create another baseline and compare it with the previous one Outcome An APM application view and/or Insights Dashboard that proves an application is (any/all): faster, cheaper to operate, easier to expand, improves Apdex, or is more available. Application Refactoring Possible products based on architecture review recommendations InsightsI B Browser M SyntheticsMobile S A InfrastructureAPM I
- 10. ©2008–18 New Relic, Inc. All rights reserved 10 Run Purpose Provide a Dashboard to showcase improvements in the customer’s experience. The underlying work for this may be carried out through the Application Refactoring process. However, for this one, the focus is on the customer facing experience. This should be done within a development environment so a comparison can be displayed. Steps 1. Identify application scoped for improvement 2. If not already done, deploy and configure Browser and Synthetics to monitor the customer facing web front end and Mobile for applications that use the cloud as the back end 3. Identify relevant metrics – based on industry 4. Create a Dashboard showing metrics for both the current production environment and the updated development environment related to customer experience Outcome An Insights Dashboard that provides the status of customer’s experience metrics comparing the updated application to the current production one. KPIs Availability percentage, Average Duration, Page Load Time, Throughput, Apdex, Response Time Optimize Customer’s Experience Possible products based on architecture review recommendations Insights B Browser SyntheticsS A InfrastructureAPM II M Mobile
- 11. ©2008–18 New Relic, Inc. All rights reserved Amazon EC2 Instance Server (Virtual) Hardware Server OS Application & Application Microservices DASHBOARDS New Relic + Amazon CloudWatch New Relic Application Monitoring New Relic Infrastructure Monitoring Amazon CloudWatch New Relic Monitors CloudWatch monitors NR Integrations Amazon CloudWatch Integrations • Visibility into virtualization • CPU / Disk / Networking • Popular AWS Services New Relic • CPU / Disk / Networking • Memory / Filesystem • Processes - Infrastructure components - Configuration inventory • Application / Microservices: - Latency - Error rates - App insights Browser Mobile 11
- 12. Thank You ©2008–18 New Relic, Inc. All rights reserved linkedin.com/in/boris-gouchev @gouchev