“Observability for developers: How to get from here to there” with @cyen!
#VelocityConf
We are talking a bit about the Dev/Ops wall and @cyen’s experience of developing *so* fast... and how that sometimes turns into the stereotype of devs breaking things.
#VelocityConf
Unsurprisingly, one of the biggest triggers of of incidents is the act of generating change.
m.subbu.org/incidents-tren…
#VelocityConf
There are two waves to the DevOps. The first? Get ops to code. Second? Teaching devs to own their product in production.
#VelocityConf
We are getting into the differentiation between monitoring and observability. As @cyen puts it “Why is my system doing this thing and why isn’t it what we expect?”
#VelocityConf
On to Observability Driven Development!
So is that ODD, OdieD, or o11yDD?
#VelocityConf
What is OdieD? Using an understanding of how your code performs in the wild to inform development practices and ensuring that you have that visibility!
#VelocityConf
How do we get to a world where production is a natural “playground” for devs?
1 Get context for events in a structured manner
2 Get started with adding high cardinality data to events as they enter the system
3 Stop searching, start visualizing
4 Trace trace trace
#VelocityConf
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.