Zero-Code Instrumentation of an Envoy TCP Proxy Using eBPF

Could you not have gotten all this information by changing the Envoy log format to add the required fields? In your blog post, you show the default log format, and suggest that there was no way whatsoever to get this data from the logs. But according to the documentation, Envoy has rich support for many additional fields including detailed latency statistics.

I wonder if you added complexity to the architecture when a simple log format change would have sufficed.

Great article! What is the name of tool used for writing the block diagram?

Great post, thanks for sharing! I appreciate all the details, including context for the problem, the complete setup, and the results. Bookmarked for future reference.

I was also on the verge of installing OBI to troubleshoot networking issue on one of our clusters. So maybe next time there’s a similar incident