envoyproxy/envoy

Monitor / view current TCP connection routing for long lived connections

Open

#6,259 opened on Mar 12, 2019

View on GitHub
 (3 comments) (2 reactions) (0 assignees)C++ (5,373 forks)batch import
enhancementhelp wanted

Repository metrics

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

Description

Note: This might be related to https://github.com/envoyproxy/envoy/issues/3818 .

Using envoyproxy/envoy:v1.9.0 .

We have a requirement / enhancement request to see what TCP connections are currently active. What would quickly help us out, is to add an option to the access logger to log at (established) connect time, next to the disconnect time.

To be able to query the admin API for this would be great as well.

More details:

We use Envoy for long lived TCP connections, with two-way trust and SNI. Via SNI, a dedicated cluster is selected, via filter_chain_match. TCP connections are long lived (can be days). Currently, the access logger only logs at disconnect (and for stats like bytes_recieved this makes sense).

Contributor guide

Research direction
Explore the access logger code in Envoy to understand how to log at connection establishment time. Also review the admin API to see how to expose active TCP connections.
Tech stack
None
Domain
networkingbackend
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Envoy internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60