Observing your Observability
When did your team last look at its observability on purpose, rather than in the middle of an incident? It's easy to add instrumentation and then move on. Over time the dashboards stop matching the system, the alerts fire so often that nobody reacts any more, and the gaps in your data stay hidden until the day you need exactly what's missing. This talk shares a simple weekly habit that makes observability something the whole team looks after rather than one person's speciality, built around three questions: is anything wrong, what can we not see, and what is just noise.
Curtis Tarr
Curtis is a full-stack engineer at Gearset, working on DevOps tooling for Salesforce teams, with a background in scalable backend systems and cloud-native architecture across AWS serverless, .NET on Azure and Java SaaS platforms.