High-Resolution Platform Observability
Briefly

Brian Martin works at IOP Systems and focuses on performance and optimization, including benchmarking and profiling to improve efficiency. Multiple open-source tools originated at Twitter: Rezolus (a performance telemetry agent), Pelikan (an in-memory caching framework), and rpc-perf (a benchmarking tool). Those projects complement each other because benchmarking and observability reveal performance gaps. Martin and former Twitter peers cofounded IOP Systems to provide software testing with rich telemetry for performance insights. Prior work includes hardware and OS qualification performance testing. Observability comprises logs, metrics, and traces, but platform observability extends beyond those pillars to require visualization, analysis, reporting, and mechanisms to trigger actions or alerts.
Martin: Welcome to High-Resolution Platform Observability. My name is Brian Martin. My pronouns are he, they. I work at IOP Systems. My GitHub is github.com/brayniac. I focus on performance and optimization, which means I spend a lot of time benchmarking and profiling and trying to make things more efficient. I work on a few open-source projects. All of these actually started at Twitter: Rezolus, which is a performance telemetry agent, Pelikan, which is an in-memory caching framework, rpc-perf, which is a benchmarking tool.
When we talk about observability, people like to say that there's three pillars of observability. We have logs, which tell us when things happen. We have metrics, which give us visibility into our operating systems, our services, our hardware. We have traces that try and follow the path of one thing through our infrastructure and give us the breakdown at times. Platform observability is really more than just those three pillars.
Read at InfoQ
[
|
]