The emergence of cloud native environments has changed our platform world. Not only are you coding, but expected to deliver, maintain, and support all aspects of the platform. This change means the Ops in DevOps has been overshadowing why we got into development in the first place. There is hope for us yet if we can just manage to shift left to close the gap in our time spent on non-operational activities. How do we do that, you ask? It’s imperative that developers are given not only the organizational structure to succeed, and even more critical is the ability to reduce time on triaging failures in their deployments. Attendees will be provided with insights into DevOps cloud native tips and tricks to spending more time on projects that matter and less on call. Join us in learning how you can shift left with your DevOps activities to bring more joy to your days.
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.”
chronosphere.io
10. 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
11. chronosphere.io
“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
chronosphere.io
21. chronosphere.io
Our mission: help customers get to remediation as
quickly as possible
How quickly do
I get notified
when
something is
wrong?
Is it BEFORE a
user/customer
has a bad
experience?
01 How easily
and quickly
can I triage it
to know what
the impact
is?
02 How do I find the
underlying cause
so I can fix the
problem?
03
26. chronosphere.io
Control - Re-shape data on the fly
● Combine, downsample, and aggregate metrics
● Add, drop, change labels on metrics
● Adjust retention and resolution
● Transformed inline before storage
Customer VM
or Node
Chronosphere
Collector
Chronosphere
Control Plane
Chronosphere
Data Store
Rate
Limits
100k ingested
data points/sec
50k stored
writes/sec