Berlin

November 4 & 5, 2024

New York

September 4 & 5, 2024

London

June 16 & 17, 2025

Observability that matters (and avoiding the kind that doesn't)

The term observability has recently earned somewhat of a cult status — rapidly ascending to the ranks of “agile”, “digital transformation”, “microservices” and other such highly regarded (and perhaps often misused) labels. Suddenly every team wants to incorporate the pillars of observability into their ecosystem.

Speakers: Tom Oketch

Register or log in to access this video

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register
July 31, 2020

The term observability has recently earned somewhat of a cult status — rapidly ascending to the ranks of “agile”, “digital transformation”, “microservices” and other such highly regarded (and perhaps often misused) labels. Suddenly every team wants to incorporate the pillars of observability into their ecosystem.

But observability for observability’s sake has no inherent benefits. What is the goal of being able to dissect your services or trace transactions across multiple service boundaries? How do these newfound principles and practices translate into meaningful actions and outcomes? And how can you make sure you’re not falling into the trap of the bandwagon fallacy?

This talk explores some of the emerging anti patterns around observability, their pitfalls, and how to avoid them. It also explores how teams can focus on achieving the right kind of insight into how their systems are performing and being utilized – observability that matters.