DevOps Paradox cover image

DOP 201: Getting to the Root Cause With Zebrium

DevOps Paradox

00:00

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.

Transcript
Play full episode

The AI-powered Podcast Player

Save insights by tapping your headphones, chat with episodes, discover the best highlights - and more!
App store bannerPlay store banner
Get the app