"Observability is the capability to continuously generate and discover actionable insights based on signals from the system under observation with the goal to influence that system" and that's for both people (eg debugging) and automation (eg autoscaling) @mhausenblas#QConLondon
Observability can go beyond usual metrics, logs and traces: @mhausenblas introducing profiles and eBPF #QConLondon
Profiles with sampling are low overhead, so great to apply in production. @mhausenblas#QConLondon
High-level architecture of Continuous Profiling, from agent and ingestion to frontend for visualisation. @mhausenblas#QConLondon
Continuous Profiling with Parca, open source project, with concepts and query language very close to Prometheus. @mhausenblas#QConLondon
Looking ahead, eBPF is becoming the unified collection method for profiles. Profiling standards seem to be converging towards pprof with its increasing support @mhausenblas#QConLondon
Correlation remains a challenge with profiles, to link together all the different signal types, rather than dealing with multiple independent tools. @mhausenblas#QConLondon
Here we go, last talk of the day on the production track at #QConLondon, with @rdelvira and "an entertaining outage story" (his own words) when slack rolled out DNSSEC
"Who here tried to rollout DNSSEC?, Ok one person... Now how failed when trying to rollout DNSSEC? Welcome to the club!" 😂 @rdelvira#QConLondon
"We planned DNSSEC carefully, with the necessary changes and replicated most of our DNS use cases... And you'll see later why I said 'most'..." @rdelvira#QConLondon
Continuing the #QConLondon production track with @yurynino, and using visual metaphors to understand our production data in a different way.
"In our field, observability is about humans and about how humans interact with technology" @yurynino#QConLondon
Collecting metrics and signals are only one part of the solution - observability has to come with good visualisation, and engineering a solution for humans. @yurynino#QConLondon
First talk of the day on the #QConLondon production track, by @glenathan and a challenge: can we build observable services without logs?
"We needed to build a new service in Go, without our usual existing scaffolding in Clojure... That led to some bikeshedding but also gave a chance for experimentation!" @glenathan#QConLondon
"Before this, we spent a lot of money to know what our applications were doing in production"