envoyproxy/envoy

Some of listener's statistics can support to be collected per dst ip

Open

#21,258 opened on May 12, 2022

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/listenerarea/statshelp wanted

Repository metrics

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

Description

Description: As envoy works as proxy, which means all of the connections can use just one listener, this makes all of IP's statistics are all put together to the statistics of listener. This is not easy to figure out when there are just some of the ip's are having the issue like TLS handshake error. In TLS level, there is already connections info, so some of the statistics can be exposed with ip infos.

If envoy can supports to enhance some of listener's statistics to be collected per dst ip, then it should be helpful to debug issues

Contributor guide

Research direction
Examine how listener statistics are currently collected and identify where per destination IP statistics could be added. Familiarize yourself with Envoy's stats interface and consider how to extend it without breaking existing behavior. Look at similar per connection TLS statistics for guidance.
Tech stack
cpp
Domain
backendnetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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 internalsStatistics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60