AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
3min chapter
DOP 201: Getting to the Root Cause With Zebrium
DevOps Paradox
What's the Classic Workflow?
Knowing symptoms is just the starting point, which has value because at least you can get to work before your company's name starts to show up on down detector or on Twitter. The classic workflow we see from people is when they become aware of a problem, they will try and use their dashboards and metrics to first narrow down the timeframe. So if it's a latency spike, you'll notice at what point in time did the latency start climbing? That's maybe the beginning of your problem period. And so that sort of narrows down the domain and maybe the subset of your organization that needs to focus on the problem.
00:00
Transcript
Episode notes
Get the Snipd
podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered
Discover
highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any
moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share
& Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
Discover
highlights
Listen to the best highlights from the podcasts you love and dive into the full episode