Whether you’re an enterprise migrating to cloud native or born in the cloud, most of today’s APM and Observability tools don’t support how your engineers and DevOps teams need to develop, deploy, and support their software. Observability needs to shift left and reflect the modern way companies organize their development teams and their vital interdependencies. Chronosphere is the only vendor addressing the unique requirements for observability in a cloud native world. Join this webinar to learn: - What cloud native observability is and how it is different from the promises made by traditional cloud APM and observability vendors - How to use cloud native observability to do more “Dev” and less “Ops” so you can dramatically improve developer and engineer workflows and productivity - How to make on-call shifts less stressful so your engineers aren’t getting burned out

1. chronosphere.io
Shift Left Observability
Eric Schabell
Director Evangelism
@ericschabell{@fosstodon.org}
George Hamilton
Director Product Marketing
@eghamilton
Discover true cloud native
observability
chronosphere.io

2. Evolution of the monitoring market
Gen 1
On-Premises
(Data center)
1998 - 2008
Gen 2
Cloud
(IaaS, VM-based)
2008 - 2018
Gen 3
Cloud Native
(Microservices and Containers)
2018 - ?
1 Monolith
10s Hosts
10s Services
1,000s VMs
1,000s Microservices
1,000,000s Containers
Is it up or down? Is it performing in
line with SLA/SLOs?
What is the
customer/end user
experience?

3. chronosphere.io
Cloud native complexity is overwhelming

4. chronosphere.io
Cloud native complexity is overwhelming

5. chronosphere.io
Cloud native complexity is overwhelming

6. chronosphere.io
Cloud native complexity is overwhelming

7. chronosphere.io
Cloud native complexity is overwhelming

8. chronosphere.io
Cloud native complexity is overwhelming

9. chronosphere.io
Cloud native complexity is overwhelming
Customer

10. chronosphere.io
Cloud native complexity is overwhelming
Customer

11. chronosphere.io
Cloud native complexity is overwhelming
Customer

12. chronosphere.io
Cloud native complexity is overwhelming
Customer
Longer time to resolve
problems

13. chronosphere.io
Cloud native complexity is overwhelming
Customer
Longer time to resolve
problems

14. chronosphere.io
Cloud native complexity is overwhelming
Customer
Longer time to resolve
problems
Engineering toil and waste

15. chronosphere.io
Cloud native complexity is overwhelming
Customer
Longer time to resolve
problems
Engineering toil and waste

16. chronosphere.io
Cloud native complexity is overwhelming
Customer
Longer time to resolve
problems
Engineering toil and waste
Costs are increasing

17. chronosphere.io
Cloud native complexity is overwhelming
Customer
Longer time to resolve
problems
Engineering toil and waste
Costs are increasing
$*%#

18. chronosphere.io
Cloud native complexity is overwhelming
Customer

19. chronosphere.io
Cloud native complexity is overwhelming
Customer
71%
Of companies are
concerned with the
rate of growth of their
observability data
Source: ESG

20. chronosphere.io
Cloud native complexity is overwhelming
Customer
71%
Of companies are
concerned with the
rate of growth of their
observability data
Source: ESG

21. chronosphere.io
Cloud native complexity is overwhelming
Customer
Of companies have
seen an increase in the
number of customers
impacting digital
incidents in the last 12
months
Source: PagerDuty
71%
Of companies are
concerned with the
rate of growth of their
observability data
Source: ESG
68%
$*%#

22. chronosphere.io
Today’s observability tools are failing cloud native teams
and organizations
Overwhelming
data volume
Workflows not
aligned to organization
Longer troubleshooting
times
Dashboards & queries load
slow or not at all
Engineer burnout is
getting worse

23. chronosphere.io
Feel like the water (data)
is rising around you?

24. chronosphere.io
The struggle is real
“I don't yet collect spans/traces because I can hardly get our devs to care about basic
metrics, let alone traces.”
“This is a large enterprise with approx. 1000 developers. Cultivating a culture of
engineering that cares about availability is a challenge that we need to solve alongside
any technical implementations.”

25. chronosphere.io
Microservice Microservice Microservice
Microservice Microservice Microservice
Virtual Machine
Application
Infrastructure
Microservice Microservice Microservice
Microservice
Microservice
Microservice
1:1
1:1 M:M
M:M
Product / Service
Use Cases Experiment Clients Geography
Business
Cloud
(IaaS, VM-based)
2008 - 2018
Cloud Native
(Microservices and Containers)
2018 - ?
Legacy monitoring built to
handle this level of complexity
Cloud-native monitoring built to handle
this level of complexity
Cloud native impact on data volume
Monolith
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR
CNTR

26. chronosphere.io
High cardinality runs wild in cloud native environments

27. chronosphere.io
Experiment:
● Hello World app on 4 node
Kubernetes cluster with
Tracing, End User Metrics
(EUM), Logs, Metrics
(containers / nodes)
● 30 days == +450 GB
chronosphere.io

28. chronosphere.io
Workflows are not
aligned to your organization

29. chronosphere.io
How did we get here? Cloud native!
Software development: cloud

30. chronosphere.io
How did we get here? Cloud native!
Software development: cloud Software development: cloud native

31. chronosphere.io
But cloud native monitoring increases entropy
App App
Monitoring: cloud Monitoring: cloud native

32. chronosphere.io
But cloud native monitoring increases entropy
App App
Monitoring: cloud Monitoring: cloud native

33. chronosphere.io
But cloud native monitoring increases entropy
App App
Monitoring: cloud Monitoring: cloud native

34. chronosphere.io
But cloud native monitoring increases entropy
App App
Monitoring: cloud Monitoring: cloud native

35. chronosphere.io
But cloud native monitoring increases entropy
App App
Monitoring: cloud Monitoring: cloud native

36. chronosphere.io
But cloud native monitoring increases entropy
App App
Monitoring: cloud Monitoring: cloud native

37. chronosphere.io
But cloud native monitoring increases entropy
App App
Monitoring: cloud Monitoring: cloud native

38. chronosphere.io
But cloud native monitoring increases entropy
App App
Monitoring: cloud Monitoring: cloud native

39. chronosphere.io
Where do we need to go?
Dashboard and tool sprawl
What we have What we need
Data locked in proprietary formats
Platform dictates data collection
Over-reliance on power users & toil
Monitoring tools lack reliability and scale
● Faster troubleshooting times
● Excellent application experience
● Happier, more productive engineers
Centralized control with flexibility
100% open source compatibility
Service owners choose data (with guidelines)
Empowered engineering teams & innovation
Better reliability than production systems
● Longer troubleshooting times
● Poor application experience
● Engineer burnout & turnover

40. chronosphere.io
Cloud native complexity is overwhelming
Customer

41. chronosphere.io
Cloud native complexity is overwhelming
Customer
71%
Of companies are
concerned with the
rate of growth of their
observability data
Source: ESG
68%
Of companies have
seen an increase in the
number of customers
impacting digital
incidents in the last 12
months
Source: PagerDuty

42. chronosphere.io
Chronosphere puts you back in control!
Customer

43. chronosphere.io
Chronosphere puts you back in control!
Customer
INFRASTRUCTURE // CONTAINERS
APPLICATION // MICROSERVICES
BUSINESS

44. chronosphere.io
Chronosphere puts you back in control!
Customer
INFRASTRUCTURE // CONTAINERS
APPLICATION // MICROSERVICES
BUSINESS
Control and
efficiency of data

45. chronosphere.io
Chronosphere puts you back in control!
Customer
INFRASTRUCTURE // CONTAINERS
APPLICATION // MICROSERVICES
BUSINESS
Devops spend half as much
time on troubleshooting
Control and
efficiency of data

46. chronosphere.io
Chronosphere puts you back in control!
Customer
INFRASTRUCTURE // CONTAINERS
APPLICATION // MICROSERVICES
BUSINESS
Devops spend half as much
time on troubleshooting
Control and
efficiency of data
Increase ROI on
observability

47. chronosphere.io
Chronosphere puts you back in control!
Customer
INFRASTRUCTURE // CONTAINERS
APPLICATION // MICROSERVICES
BUSINESS
Devops spend half as much
time on troubleshooting
Control and
efficiency of data
Increase ROI on
observability
Happy Days!!!

48. chronosphere.io
Contextualized
views per user
TRIAGE ROOT CAUSE ANALYSIS
NOTIFICATION
Chronosphere Platform
Data Store
Single tenant
architecture, proven
industrial reliability
and scalability
Metrics
Events
Traces

49. chronosphere.io
Contextualized
views per user
TRIAGE ROOT CAUSE ANALYSIS
NOTIFICATION
50% less time spent
troubleshooting
Chronosphere Platform
Data Store
Single tenant
architecture, proven
industrial reliability
and scalability
Metrics
Events
Traces

50. chronosphere.io
Contextualized
views per user
TRIAGE ROOT CAUSE ANALYSIS
NOTIFICATION
50% less time spent
troubleshooting
48% average data
reduction after transformation
Chronosphere Platform
Data Store
Single tenant
architecture, proven
industrial reliability
and scalability
Metrics
Events
Traces

51. chronosphere.io
Contextualized
views per user
TRIAGE ROOT CAUSE ANALYSIS
NOTIFICATION
50% less time spent
troubleshooting
48% average data
reduction after transformation
Proven to scale to 1.5B data
points per second
Chronosphere Platform
Data Store
Single tenant
architecture, proven
industrial reliability
and scalability
Metrics
Events
Traces

52. chronosphere.io
Contextualized
views per user
TRIAGE ROOT CAUSE ANALYSIS
NOTIFICATION
50% less time spent
troubleshooting
48% average data
reduction after transformation
Proven to scale to 1.5B data
points per second
99.99% historically
delivered uptime
Chronosphere Platform
Data Store
Single tenant
architecture, proven
industrial reliability
and scalability
Metrics
Events
Traces

53. chronosphere.io
Control observability data
Control data growth by optimizing volume, dimensionality and aggregation
Rate
Limits
100k data
points/sec
(example)
50k transformed
data points
/sec (example)
Chronosphere
Collector
Chronosphere
Control Plane
Chronosphere
Data Store
An observability control plane gives you:
● Drive greater engineering efficiency
and quality of life
● Optimize cost and performance
● Bend the curve of future data growth
● Tailor retention and resolution
● Rate Limiting, Quality of Service
protection & Quota Limits

54. chronosphere.io
A new, team-centric approach

55. chronosphere.io
Chronosphere is the only cloud native observability
solution that unlocks competitive advantage
The leading cloud native companies use Chronosphere enterprise-wide
World class
customer
success
Control and
shape your
data
Most reliable
platform
Fastest to
detect, triage,
root cause
Right data in
the right
context

56. chronosphere.io
Case Study
Chronosphere partnered with Robinhood’s central observability team to provide
more effective insights, monitoring and data control of their systems.
4x
Improvement in mean
time to detect
$15M
Saved compared to
running in-house
8x
query latency
improvement
75%
of critical incidents
eliminated

57. Questions?

58. chronosphere.io
Resources from Chronosphere
● Case Studies
○ DoorDash Case Study
○ Genius Sports Case Study
● More resources
○ Ebook:Get the facts about cloud native observability
○ Forrester Study: Total Economic ImpactTM Report of Chronosphere
○ Blog: APM Vendors are creating confusion about observability. Don’t
fall for it.
● Talk to an Observability expert at Chronosphere
○ Schedule a conversation