Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Observability
Search
Daniel Temme
May 06, 2024
0
42
Observability
Talk from DevConf 2024
Daniel Temme
May 06, 2024
Tweet
Share
More Decks by Daniel Temme
See All by Daniel Temme
Lean Startup Rubyfuza
dmt
4
140
Featured
See All Featured
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
331
22k
Speed Design
sergeychernyshev
32
1k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
2.9k
Building Flexible Design Systems
yeseniaperezcruz
328
39k
Optimising Largest Contentful Paint
csswizardry
37
3.3k
Site-Speed That Sticks
csswizardry
10
690
Product Roadmaps are Hard
iamctodd
PRO
54
11k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
233
17k
YesSQL, Process and Tooling at Scale
rocio
173
14k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
35
2.4k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
Transcript
Making Observability Tangible with the help of test automation
None
(slides and references are available online) Why I f ind
the topic interesting O11y 101 (a brief intro and some ideas) A playground to experiment Agenda
https://unsplash.com/photos/time-lapse-photo-of-lighted-ferris-wheel-at-park-during-nighttime-WnADr2BG174
(Reenactment) A long time ago...
https://unsplash.com/photos/yellow-and-black-bird-on-brown-wooden-post-q77K0zIDTmI
https://unsplash.com/photos/photography-of-theater-chairs-e_RpjNyMgEM
https://web.archive.org/web/20110128133821/https://www.net f lix.com/
Please hold for a brief interruption https://unsplash.com/photos/white-and-red-plastic-packs-9FDI-_E29 f k
The o11y building blocks O`bservabilit | wc - l `y
• Metrics • Traces • Logs
Metrics • High rate of events, with low cardinality at
a reasonable cost • Gauges and counters (and distributions/histograms from those) • Think CPU load, temperature, durations, number of requests
Traces • Medium rate of events, supplement metrics • Durations
across systems • Think waterfall graphs and pro f ilers (which some APM tools now also include in trace data)
Logs • Lower rate of events for comparable cost to
metrics but with higher cardinality of related data • Ideally structured, ideally one line per service per request
Lower level questions What questions to ask? • which of
my hosts have high cpu load? • which service is giving a lot of 500 error responses? • where is the time spent on this queue processing an event?
Slightly broader questions What questions to ask? • when will
I run out of my error budget for my SLO? • how many items are we selling compared to the same time last month? • how many instances can we turn off?
Higher level questions What questions to ask? • how much
of our daily sales are from repeat customers? • how many streams do our customers play on average per month over time? • how much are we paying per request handled?
https://unsplash.com/photos/a-sign-that-is-on-the-side-of-a-hill-jCfDzOQ2-C8
Considerations A sample project • Needs to be actively maintained
• Needs to run locally • Needs to mostly maintain itself