The Humans of DevOps Podcast Series S1 Ep23: Domain-Oriented Observability
Aug 18, 2020
Siddharth Pareek, VP of Consulting and Global Practice Lead for DevOps CoE at NatWest Group, delves into the transformative world of domain-oriented observability. He highlights the shift from traditional monitoring to aligning observability with business objectives, enhancing customer experiences. The conversation emphasizes integrating business values into technical metrics, fostering collaboration between IT and business teams. Pareek shares practical strategies for developers and illustrates the evolving skills needed in today's landscape, making observability a crucial business-centric pursuit.
AI Snips
Chapters
Books
Transcript
Episode notes
Observability Connects Tech To Business
- Observability shifts focus from technical signals to business outcomes that matter to customers.
- If a system is observable, teams can monitor business-relevant behavior instead of just CPU or server metrics.
Use Domain Language For Observability
- Domain-oriented observability uses the ubiquitous language of the domain to describe system behavior.
- This makes observability cleaner and more relevant by avoiding overly technical SME-driven instrumentation.
Start Observability In Development
- Instrumentation belongs with development because the app lifecycle starts in dev.
- Adopt existing language implementations and community solutions rather than inventing ad-hoc approaches.
