, 7 tweets, 2 min read Read on Twitter
A: Yes, there are many aspects of instrumentation and observability that are worth investing in, even for monoliths. Distributed systems are just where the pain of *not* doing so becomes prohibitive.
This is largely for historical reasons. Due to hardware cost, we optimized for skimpy metrics data, and generations of engineers grew up fitting their thinking and tooling around scarce data types like metrics instead of richer event-trace data.
It is categorically easier to debug and understand your systems with o11y than with scattered, aggregated/averaged/aggregated metrics.

It's incredibly hard to form a mental reconstruction (or hazard a few guesses) about why events are erroring when all you have are dashboards.
It's much easier to simply ask a straightforward question. Which you can do if you gathered the data by event in the first place.

Instead of seeing some spikes and running through a library of guesses as to the cause, you just ask. Compare:
Old way being: "I see a latency spike. Is it mysql timing out? Is it a memcache issue? Is it us-east-1? Is it coming from apps running an old version of the code?"

as you flip through dashboards one by one to check for data to support your hypotheses
With events, it goes more like this: "I see a latency spike. I will circle it with the mouse, and -- aha, those errors are all timeouts to the /export endpoint from a test user exceeding the upload limit"

(ok I sorta cheated, that's using bubbleup instead of iterating)
The point is: you don't have to guess or imagine sprawling abstractions. The data
Is right in front of you.

It takes a little work to unlearn old habits. But new grads and people who haven't done hard time in ops tend to find it much easier and more intuitive than the old ways.
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Charity Majors
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!