Observability
posts (6)
- Part II: Standardizing AI in the SDLC Across the Organization8/10
Observability, security and control
With dozens of agents you need every model call, tool call and RAG document as a span in a trace, control over input and output at the tool boundary, and…
- The Layers of HTTP in the Browser: From fetch() to QUIC9/9
From fetch() to the First Byte
The whole lifecycle in one place: browser policies, cache, connection, wire format, headers and body. Only with that model does the Network panel answer…
- CPU in Kubernetes from the kernel up12/12
Anatomy of a CPU problem: from an understated request to p99 latency
One incident end to end: a 500m request, no limit, no throttling, and p99 climbing from 35 to 180 ms. The whole path of the mechanism.
- CPU in Kubernetes from the kernel up10/12
How to debug CPU in Kubernetes without guessing
Usage, throttling, contention and pressure are four different phenomena. A single CPU chart settles none of them - you need an order of operations.
- CPU in Kubernetes from the kernel up6/12
PSI: how Linux measures real CPU pressure
Utilisation says how much CPU a workload got. PSI measures the time it lost because it wanted to execute and had nothing to execute on.
- Testing Through Layers: From Code to Infrastructure8/9
Performance Tests and Load Tests: Behavior Under Traffic
A performance test measures system behavior over time, a load test checks expected traffic, and a stress test looks for the breaking point.