Observability remains one of the last bastions of the infamous “wall of confusion” between development and operations. The DevOps movement redefined engineering responsibilities—developers now deploy their own code and are on-call for it—but one outdated expectation remains: that SREs should handle observability and monitoring for everyone. This imbalance not only overburdens SRE teams, it also undercuts the organization’s return on observability investments—leaving valuable data and tools underutilized and teams struggling to connect data to decisions.

Join Chronosphere’s Paige Cruz, Principal Developer Advocate, for a fireside chat on how and why SREs can evolve from reactive support roles into stewards of observability strategy. We’ll explore how to determine ‘just enough’ observability fluency for developers, approaches to embedding observability into internal platforms, and how leading hands-on tutorials and documentation can reduce support toil and enable better engineering outcomes.

Attendees will learn what contributes to observability knowledge silos—and discover tactical ways to break them down—so teams can build shared understanding without contributing to burnout.