The document outlines three major pitfalls organizations face with cloud data: misunderstanding bandwidth and storage needs, lacking observability across cloud landscapes, and not knowing the costs linked to observability metrics. It emphasizes the necessity of cultivating a culture of engineering that values availability and establishing a dedicated FinOps function to maximize resource value. Additionally, it provides a framework for cloud migration, stressing the importance of establishing a baseline for cloud landscape management.

1. chronosphere.io
3 Pitfalls
Eric D. Schabell
Director Evangelism
@ericschabell{@fosstodon.org}
Everyone Should Avoid with Cloud Data
chronosphere.io

2. chronosphere.io

3. chronosphere.io

4. chronosphere.io
1. Cloud & data

5. chronosphere.io
Does your company know their
bandwidth and storage needs?
What about the cost?
Question #1
Something to think about...

6. chronosphere.io
De Persgroep
(Based on audience question from ‘Power to Innovate talk)
“Why don’t you go 100% to cloud for hosting your news group
assets?”
The quoted price for hosting was OK, but the bandwidth quotes
were off the charts.
Shortly thereafter, during the Paris attacks (Charlie Hebdo) the
French people crashed all local news sites. The Walloon (FR
Belgium) sites hosted by De Persgroep received an extra 1.2
million unique visitors…. (810K BE, 450K NL).

7. chronosphere.io

8. chronosphere.io
2. O11y is data

9. chronosphere.io
Will your organization have observability
across their cloud landscape?
Question #2
Something to think about...

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

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

12. chronosphere.io

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

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

15. chronosphere.io

16. chronosphere.io

17. chronosphere.io
3. FinOps the crucial Ops

18. chronosphere.io
Question #3
Do you know the cost of observability
metrics data?
Something to think about...

19. chronosphere.io
Dedicated FinOp
“By 2023, 80% of organizations
using cloud services will
establish a dedicated FinOps
function to automate policy-
driven observibility and
optimization of cloud
resources to maximize value.”
-- Source: IDC 2022

20. chronosphere.io
Bonus Question #4
Does your organization have a baseline
of your cloud landscape?
Something to think about...

21. chronosphere.io
1. Determine your goals of migrating data to the cloud
2. Assess your current situation
3. Select the right cloud migration partner
4. Create your business case for the cloud
5. Select the type of cloud environment needed – public, private, hybrid or
hybrid-multi?
6. Determine the specific cloud components necessary
7. Choose the right cloud provider
8. Plan the cloud approach
9. Execute the migration
10. Observability of the production environment
Don’t forget the baseline!

22. chronosphere.io

23. Questions?
Eric D. Schabell
Director Evangelism
@ericschabell{@fosstodon.org}