Notes from building
behind the firewall.
Production surprises, how things work, and what they cost — from the team building observability you run in your own environment.
Why your service map is lying to you
A service map built from TCP connections quietly misses most of your traffic: gRPC channels, keep-alive and connection pools never close, their peers are virtual IPs, and every restart of the collector forgets what was already open. Here is what we found, and what fixed it.
Read →Go 1.24 made our connection tracking miss every Go server
Since Go 1.24, Go programs on Linux listen with Multipath TCP by default. If your tooling finds sockets through a process's file descriptors and filters on TCP, every Go server's listening port quietly disappears.
Read →
Run it in your own cluster this week.
A 30-minute call, then an evaluation core on your infrastructure. You will see your own services, traces and logs — from your own traffic — before you decide anything.
- No data leaves your environment, including during the trial
- Helm install, works fully air-gapped
- You talk to the engineers who built it