Extension overhead latency breakdown
Open
area/extension
enhancement
help wanted
- Dominant language
- C++
- Stars
- 28.9k
- Forks
- 5.6k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 430
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
Assessment
This issue has not been assessed yet.