Adriana Villela

Observability may have been a newcomer few years ago, but it's safe to say that it's a pretty well-established part of our tech lives today. But as organizations add Observability to their roster, they run the risk of creating Yet Another Silo with Observability, in much the same way that DevOps created more silos, instead of breaking them.

Reliability can't happen without Observability.

Observability must be looked at holistically. It is not the sole responsibility of any one team or individual. Everyone has an important part to play, and to a certain extent, the parts weave into each other.

For leaders, understanding how Observability touches different aspects of an organization will help them craft an Observability rollout that does justice to the promise of Observability. That is: the ability to ask meaningful questions, get useful answers, and act effectively on what you’ve learned.

For practitioners, understanding how Observability touches each aspect of the SDLC will serve to inspire and empower them to contribute to the organization’s systems’ reliability.

This talk will show how Observability weaves its way into various aspects of an organization:
1. Instrumenting code
2. Managing Observability infrastructure
3. Making CI/CD pipelines observable
4. Troubleshooting code

It will also show how an “Observability team”, if not designed and rolled out properly, can take away an organization’s collective responsibility for Observability, and dilute the promise of Observability.