Observability for emerging infra: what got you here won't get you there




Distributed systems, microservices, containers and schedulers, polyglot persistence .. modern infrastructure patterns are fluid and dynamic, chaotic and transient. So why are we still using LAMP-stack era tools to debug and monitor them? We’ll cover some of the many shortcomings of traditional metrics and logs (and APM tools backed by metrics or logs), and show how complexity is their kryptonite.

So how do we handle the coming complexity Armageddon? It starts with a more modern approaches to observability, such as client-side structured data and event-driven debugging, distributed tracing, and more; no matter how many tags you add to a metric store, it still can’t tell a story like events can. It also means shifting perspective away from “monitoring” and to “instrumentation”.

Most problems are transient or self-healing, and you cannot possibly alert on (or even predict) the long tail of possible partial failures. So you need to turn finding arbitrarily complex causes into a support problem, not an engineering problem. How? Well … that’s the fun part.

Speaker

charity-majors

Charity Majors

   
Charity is a co-founder and engineer at Honeycomb.io, a startup that blends the speed of time series with the raw power of rich events to give you interactive, iterative debugging of complex systems. ...