StackState had a blast at this year's KubeCon + CloudNativeCon gathering in Paris! The discussions were in-depth, covering a wide array of topics and lasting much longer than in the past. This year, attendees seemed to have a considerably deeper understanding of the cloud-native ecosystem, probably attributed to its rapid growth. We also noticed a pretty dramatic evolutionary shift in the vendors at the expo hall, who were showcasing some truly progressive specialized solutions.

In one of our latest posts, StackState Co-Founder Mark Bakker described how eBPF revolutionizes observability and how StackState’s agents rely heavily on eBPF to capture and analyze the data moving through your cluster. Today, we’re looking at an example where our eBPF code failed and — by diving deep into the intricacies of eBPF implementation in the Linux kernel — share the tale of how we fixed it using even more eBPF.

In the complex and fast-paced world of application deployment, getting a handle on the tangle of services and resources can sometimes feel like trying to find your way through a maze without a map. And if something goes wrong, trying to find out what's happening where is even more difficult. With alert emails flooding in and questions flying left and right, identifying the glitch that's causing issues can seem like a Herculean feat.