Whether just planning, in the middle of, or already in the cloud, going through a cloud adoption journey is a constant stress for many business owners large and small. Without a plan to monitor your cloud adoption, progress stalls, unknown issues appear, you can't prove success, and are unable to realize the cost savings and advantages you were expecting. The existing methodology of implementing monitoring at the end is actually slowing down your cloud adoption journey. This presentation covers the best practices to monitor your cloud adoption. Best practices that will give you the confidence to migrate to the cloud successfully.

1. ©2008–18 New Relic, Inc. All rights reserved

2. ©2008–18 New Relic, Inc. All rights reserved
The Earlier You Instrument,
The Faster You Go

3. ©2008–18 New Relic, Inc. All rights reserved 3
Who Am I?
Kevin Downs
Principal Cloud Strategist
21 years in industry
Specializing in:
SaaS
Cloud Adoption
12 years as a Solutions Architect
Infrastructure & Application Monitoring
Had apps in both MacOS and iOS stores
linkedin.com/in/kevin-downs@kupsand

4. ©2008–18 New Relic, Inc. All rights reserved 4
A common tale...we’ll monitor after
Where
monitoring is
(mistakenly)
recommended
today
Plan Migrate Run

5. ©2008–18 New Relic, Inc. All rights reserved 5
A common tale...help, something went wrong
Where
monitoring is
(mistakenly)
recommended
today
Plan Migrate Run
Where
it’s usually
added

6. ©2008–18 New Relic, Inc. All rights reserved 6
A common tale...in hindsight
Where
monitoring is
(mistakenly)
recommended
today
Plan Migrate Run
Where
it’s usually
added
Instrumentation
should begin in
discovery
Where
it’s usually
added
Where
monitoring is
(mistakenly)
recommended
today
Plan Migrate Run

7. ©2008–18 New Relic, Inc. All rights reserved 7
Cloud Adoption Solution Guide - Overview
Plan 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
Deploy,
visualize,
modernize,
and optimize
faster
Right size
usage 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
Modern &
Cloud Services
Application
Refactoring
Optimize
Customer’s
Experience
Prioritize
Migration
Order
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
Application
Baseline

8. ©2008–18 New Relic, Inc. All rights reserved 8
Cloud Adoption Solution Guide - Overview
Plan 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
Deploy,
visualize,
modernize,
and optimize
faster
Right size
usage 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
Modern &
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

9. ©2008–18 New Relic, Inc. All rights reserved
Application Baselining
9
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
Insights Dashboard showing current state KPIs for each product recommended
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
Plan
InsightsI B Browser M SyntheticsMobile S A InfrastructureAPM I
Possible products based on architecture review recommendations

10. ©2008–18 New Relic, Inc. All rights reserved 10
KPIs – Business and Technical – Are Critical
Corporate KPIs
• Perceived Load Time
• Apdex
• Error %
• Mobile Crash Rate
• Route Searches
• Segments
• Check Ins
• Fare Class
• Promotions
• Point Redemptions
• Complementary
Services
• Travel Packages
• Loyalty Program
Sample KPI Facets
• Geography
• XYZ Business Unit
• XYZ Product
• Device Type
• Os Type
• Mobile Platform
• Carrier
• Website Name
• Page Name
• Browser Type
• Error Type
• Application Name
• Cloud Provider
• Host
• Success/Fail Reason
Application / Infra
• ApDex
• Availability
• Throughput
• App/API/DB
Response Times
• Error %
• Memory Footprint
• CPU Workload
• Disk Workload
• Network Throughput
DevOps
• Builds
• Commits
• Deploys
• Defects
Web
• Session Count
• Session Duration
• Page Views
• DOM Readiness
• Page Render
• Perceived Load Time
• Error %
• ApDex
Trends
• Active Users
• Response Times
• Session Durations
Mobile
• App Launches
• User Counts
• Load Time
• Response Time
• Crash Rates
• Crash Locations
• Error Rates (HTTP,
Network)
• API Errors
• Session Duration
Support
• Support Incidents
• MTTI
• MTTR
• Cost per Incident

11. ©2008–18 New Relic, Inc. All rights reserved 11
Purpose
The detection of errors or possible issues with the application architecture,
scale, or performance early in a migration.
Steps
1. Identify components of the application that can be instrumented
2. Identify business KPI
3. Deploy and configure products including alerting
4. Setup integrations to cloud services
5. Monitor for issues and roadblock
Outcome
Contain migration implementation costs
The early detection of issues and roadblocks will allow for a quicker and
smoother migration as you move to a cloud based architecture. Uncovering
and solving issues early will help contain costs.
For identifying issues and roadblocks you are looking for metrics that are
highly out of scope (see KPIs on next slide for examples of metrics).
Examples:
1. Instances with very low CPU may indicate that you are using instances
that are too large
2. Very long response or transaction times may indicate an architecture that
is not optimized
3. Cloud costs that are exceeding normal thresholds may indicate an
incorrectly configured auto-scaler
Migrate
Identify Issues & Roadblocks
InsightsI B Browser M SyntheticsMobile S A InfrastructureAPM I
Possible products based on architecture review recommendations
Part 1 of 2

12. ©2008–18 New Relic, Inc. All rights reserved 12
Migrate
KPIs
Based on the recommended product(s) used...
Availability percentage, Average Duration, Page Load Time, Throughput,
Web transaction time, Throughput, Apdex, CPU percentage, Average
Load, Memory Used Percentage, Cloud Spend, Response Time
In addition to the above product KPIs, you will now have the ability to
monitor cloud based metrics.
Cloud Integrations will pull in usage, errors, and inventory data for different
cloud services and offer pre-built dashboards for these services.
With integrations, you can easily do the following:
• Monitor Usage stats: Monitor usage stats of different cloud services
e.g. how many instances, volumes, load balancers, and serverless
functions are used in different regions and ability zones
• Monitor Error Statistics: Monitor any errors seen in cloud services
(e.g. DNS health check, serverless function invocation errors/throttles
etc.)
• Alerting: You can create alerts on any of the metrics (usage/errors)
pulled in by New Relic Integrations
Create custom dashboards: In addition to the pre-built dashboards, you
can create custom dashboards (to monitor specific KPIs for any supported
cloud service)
Identify Issues & Roadblocks
InsightsI B Browser M SyntheticsMobile S A InfrastructureAPM I
Possible products based on architecture review recommendations
Part 2 of 2

13. ©2008–18 New Relic, Inc. All rights reserved 13
Purpose
Prove success (or lack thereof) by comparing the on-premises application
baseline against the on cloud application baseline.
Multiple baselines may be used for comparison if multiple products were used
to baseline the on-premises application.
Steps
1. Follow the Baselining Customer Current Experience process
2. Repeat that process for the migrated application(s)
3. Define a Dashboard that contains widgets for each product used
to show both the before and after migration baselines
Additional step as necessary:
4. Use APM to uncover any errors or issues with your applications
Outcome
One Insights Dashboard for each migrated application showing both the pre
and post migration baselines.
KPIs
Based on the product(s) used…
Availability percentage, Average Duration, Page Load Time, Throughput,
Web transaction time, Throughput, Apdex, CPU percentage, Average Load,
Memory Used Percentage, Response Time
Migrate
Acceptance Testing
InsightsI B Browser M SyntheticsMobile S A InfrastructureAPM I
Possible products - products used for Acceptance Testing will be the same products used to baseline on-premises

14. ©2008–18 New Relic, Inc. All rights reserved 14
Purpose
Capture, understand, and use both infrastructure and cloud spend collected
data to monitor the progress of right sizing your environment.
Steps
1. If not already done, deploy Infrastructure to at least one instance
2. Create Dashboard with widgets to display infrastructure metrics
related to performance and usage (CPU, Memory, Disk, DB, etc.)
3. Configure the AWS Infrastructure integration - to include Billing
4. Configure Budgets in the AWS console to track services related to
each application. Assuming, all components/services for each
application are properly tagged with application names.
5. Add Cloud Spend and Budget widgets to Dashboard
6. Optional, setup alerting including automatic baseline alerting
Outcome
All levels within the organization will have visibility to both the infrastructure as
well as the actual, forecasted, and total cloud spend KPIs corresponding to
applications or function.
Developers: Understanding of what applications are currently costing can help
to properly configure applications to use more efficient services. Examples:
Serverless functions and properly sized instances
Operators: Monitoring infrastructure usage and application costs will allow
them to catch possible overruns due to misconfigured services. Examples: auto
scaling configuration not scaling down properly or misuse of optimized
instances.
Executive: An overall view of both actual and forecasted cloud spend for both
individual applications and total costs will allow for better business decisions.
Run
Cloud Spend Optimization
InsightsI B Browser M SyntheticsMobile S A InfrastructureAPM I
Required products

15. ©2008–18 New Relic, Inc. All rights reserved 15
Baseline Alerts

16. ©2008–18 New Relic, Inc. All rights reserved
Demo
16

17. ©2008–18 New Relic, Inc. All rights reserved

18. ©2008–18 New Relic, Inc. All rights reserved

19. ©2008–18 New Relic, Inc. All rights reserved

20. ©2008–18 New Relic, Inc. All rights reserved 20
Cloud Adoption Solution Guide - Review
Plan 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

21. ©2008–18 New Relic, Inc. All rights reserved 21
Cloud Adoption Solution for AWS
Plan
Planning, Services
Selection, and Set Up
Discovery, Planning,
and Prioritization
Run, Optimize, and
Program Manage
RunMigrate
Actual
Migration
New Relic
Platform
Framework,
Dashboards
& Tools
AWS
Migration
Acceleration
Program
(MAP)
Services
Delivery
Migration Readiness
Assessment (MRA)
Migration Readiness &
Planning (MRP)
Migrations
&
Operations
(M&O)
Calibration, Baselining,
and Tracking

22. ©2008–18 New Relic, Inc. All rights reserved 22
Visit Our Booths
Venetian - 1220
Aria - Q200

23. Thank You
©2008–18 New Relic, Inc. All rights reserved
linkedin.com/in/kevin-
downs@kupsand