The daily hype is all around you. From cloud native, multicloud, to hybrid cloud, this is the path to your digital future. The choices you make as a developer does not preclude the daily work of enhancing your customer's experience and agile delivery of your applications. With all this delivery and infrastructure, there is a lot of data generated when engaging with any cloud experience. Regulatory and compliance pressures force us to store audit and observability data. Understanding the pitfalls around the collection, storage, and maintenance of your cloud data can mean the difference between bankruptcy and success with our cloud native strategy. Let us take you on a journey, looking closely at the decisions you are making as a developer delivering and dealing with monitoring your applications. Join us for an hour of power, where real customer experiences are used to highlight the three top lessons learned as their developers transitioned their data needs into cloud native environments. Key Takeaways: Attendees to this session will gain insights into the data explosion that is part of the large scale cloud native world. Real customer experiences are used to highlight the three top lessons learned as their developers transitioned their data needs into cloud native environments.

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

2. chronosphere.io

3. chronosphere.io
1. Cloud & data

4. chronosphere.io
Understand your
cloud costs?

5. 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).

6. chronosphere.io

7. chronosphere.io
2. O11y is data

8. chronosphere.io
Observability across
entire landscape?

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

11. chronosphere.io

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
https://go.chronosphere.io/2023-observability-report.html
87%
of engineers say using cloud
native architectures have
increased the complexity of
discovering and
troubleshooting incidents

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

15. chronosphere.io
88%
reporting amount of
time on issues
negatively impacts
them and their
careers

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

17. chronosphere.io
22%
said they want to quit

18. chronosphere.io
3. FinOps the crucial Ops

19. chronosphere.io
Know the cost of
observability
metrics data?

20. chronosphere.io
Dedicated FinOps
“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

21. chronosphere.io
What should be
the #1 item on
cloud wishlist?

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

23. chronosphere.io

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