All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Debugging Envoy Load Balancer Latency with eBPF Zero-Code Instrumentation

By

sergiocipriano

5mo ago· 7 min readen

Summary

The article describes a technical solution for debugging an Envoy Network Load Balancer using eBPF (Extended Berkeley Packet Filter) for zero-code instrumentation. The author faced HTTP 499 errors caused by latency in their cloud infrastructure, and Envoy's built-in options were insufficient for identifying bottlenecks. The solution involves using eBPF to instrument the TCP proxy without modifying code, allowing for detailed latency analysis and troubleshooting of network performance issues in a Load Balancer as a Service (LBaaS) environment.

Key quotes

· 5 pulled
We were seeing a small number of HTTP 499 errors caused by latency somewhere in our cloud, but it wasn't clear what the bottleneck was.
My team is responsible for the LBaaS product (Load Balancer as a Service) and, of course, we are the first suspects when this kind of problem appear.
Before going for the current solution, I read a lot of Envoy's documentation.
The options Envoy provides just weren't enough.
As a result, each team had to set up additional instrumentation to catch latency spikes and figure out what was going on.
Snippet from the RSS feed
I recently had to debug an Envoy Network Load Balancer, and the options Envoy provides just weren't enough. We were seeing a small number of HTTP 499 errors caused by latency somewhere in our cloud, but it wasn't clear what the bottleneck was. As a result

You might also wanna read