envoyproxy/envoy

Extension overhead latency breakdown

Open

#28,470 opened on Jul 18, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/extensionenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

It would be very useful for extension operators and extension writers to see how much time is spent in the extension code (Lua, Wasm, ext_proc), to troubleshoot and root cause excessive latency. At a minimum, the breakdown could be stored per request in a filter state and emitted as an access log. I think there's some code that does this for ext_proc but it needs to be generalized to other extensions.

Contributor guide

Research direction
Examine existing ext proc latency tracking code in Envoy, understand how it's implemented and stored per request, then design a generalized interface to apply similar tracking to Lua and Wasm extensions. Look at filter state management and access log formatting.
Tech stack
cppluawasm
Domain
backendinfrastructurecloud
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Envoy internalsExtension mechanism
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40