The daily choices you make as an engineer when shipping code contributes to the feedback loop. In cloud native environments a surprising amount of data is generated from the application layer down to infrastructure and along the delivery path. Regulatory and compliance pressures force us to store audit and observability data. Understanding the pressures on our engineering teams around the collection, storage, and maintenance of your cloud data can mean the difference between successful teams and burnout. Let us take you on a journey, looking closely at the current state of observability based on a recent research conducted with 500 cloud native engineers and find out what it’s like to be in the trenches.

1. chronosphere.io
chronosphere.io
Checking the Pulse
Eric D. Schabell
Director Evangelism
@ericschabell{@fosstodon.org}
of your Cloud Native Architecture

2. chronosphere.io
Cloud Native Observability

3. chronosphere.io
Cloud Native

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

5. chronosphere.io

6. chronosphere.io
Cloud Native at Scale

7. chronosphere.io
Over 66% of organizations
use more than 10 different
observability tools
– ESG report over exploding data volumes

8. chronosphere.io
“It’s remarkable how common
this situation is, where an
organization is paying more for
their observability data, than
they do for their production
infrastructure.”

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

10. chronosphere.io
10 hours
on average, per week,
trying to triage and
understand incidents -
a quarter of a
40 hour work week

11. chronosphere.io
33%
said those issues
disrupted their
personal life
39%
admitting they are
frequently
stressed out

12. chronosphere.io
Observability…

13. chronosphere.io
Cloud Native
Observability
at Scale

14. chronosphere.io
O11y at Scale (need)

15. chronosphere.io
DATA
COLLECTION
CONTROL PLANE
PURPOSE-BUILT DATA STORES
PER TELEMETRY TYPE
CHRONOSPHERE LENS
Align cost to value Single Tenanted Architecture w/
99.99% Reliability
Turns raw data into generated
insights for each user
Customer Environment Chronosphere SaaS Platform
METRICS
|
LOGS
|
TRACES
|
EVENTS
Ingest all your data from
any source

16. chronosphere.io
chronosphere.io
Questions?
Eric D. Schabell
Director Evangelism
@ericschabell{@fosstodon.org}