<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Ultraviolet Observability — Blog</title><description>What we learn building observability you run behind your own firewall.</description><link>https://uvobservability.com/</link><item><title>Why your service map is lying to you</title><link>https://uvobservability.com/blog/why-your-service-map-is-lying/</link><guid isPermaLink="true">https://uvobservability.com/blog/why-your-service-map-is-lying/</guid><description>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.</description><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Go 1.24 made our connection tracking miss every Go server</title><link>https://uvobservability.com/blog/go-1-24-mptcp-listeners/</link><guid isPermaLink="true">https://uvobservability.com/blog/go-1-24-mptcp-listeners/</guid><description>Since Go 1.24, Go programs on Linux listen with Multipath TCP by default. If your tooling finds sockets through a process&apos;s file descriptors and filters on TCP, every Go server&apos;s listening port quietly disappears.</description><pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate></item></channel></rss>