This document discusses the evolution of observability in the cloud native environment, highlighting the overwhelming complexity that organizations face today. It emphasizes that traditional observability tools are failing to meet the needs of cloud native teams, resulting in longer troubleshooting times and increased engineer burnout. Chronosphere presents itself as a solution to regain control over observability data, optimize costs, and enhance operational efficiency.

1. chronosphere.io
Shift Left Observability
Eric Schabell
Director Evangelism
@ericschabell{@fosstodon.org}
George Hamilton
Director Product Marketing
@eghamilton{@hachyderm.io}
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
Customer
Longer time to
resolve problems
Costs are
increasing
Engineering toil
and waste

8. chronosphere.io
Cloud native complexity is overwhelming
Customer

9. chronosphere.io
Cloud native complexity is overwhelming
Customer
68%
Of companies have seen
an increase in the number
of customer-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

10. 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

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

12. 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.”

13. 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

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

15. 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

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

17. chronosphere.io
How did we get here? Cloud native!
Software development: cloud Software development: cloud native
Source: https://devops.com/wp-content/uploads/2016/06/before-after-01.jpg

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

19. 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

20. chronosphere.io
Cloud native complexity is overwhelming
Customer

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

22. chronosphere.io
Chronosphere puts you back in control!
Customer
Increase ROI on
observability
Control and
efficiency of data
Devops spend half
as much time on
troubleshooting

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

24. 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

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

26. 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

27. 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

28. Questions?

29. 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