The document outlines three phases for improving observability outcomes in cloud-native environments: rapid detection of issues, effective triage with detailed information, and thorough understanding to prevent future occurrences. It highlights the challenge organizations face in managing the high costs of observability data compared to production infrastructure. The emphasis is on achieving faster remediation and enhanced customer satisfaction.

1. Three Phases to
Better
Observability
Outcomes
Eric D. Schabell
Director Evangelism
@ericschabell{@fosstodon.org}
11 Oct 2023
SRECon EU, Dublin

2. chronosphere.io
Pillars Phases

3. chronosphere.io
Developer
Technology
Bottom up

4. chronosphere.io
Pillar problems…

5. chronosphere.io
Car is on fire…

6. chronosphere.io
Observability…

7. Cloud Native
Observability at Scale

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

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

10. chronosphere.io
Better outcomes…
Faster remediation…
Easier detection…
Happier customers…

11. chronosphere.io
Phase 1
Know something
is happening as
fast as possible…

12. chronosphere.io
Phase 2
Triage with
specific
information…

13. chronosphere.io
Phase 3
Understand to
ensure never
happens again…

14. chronosphere.io

15. chronosphere.io

16. chronosphere.io
Know
Triage
Understand