TCP proxy

Dynamic cluster selection

The upstream cluster used by the TCP proxy filter can be dynamically set by other network filters on a per-connection basis by setting a per-connection state object under the key envoy.tcp_proxy.cluster. See the implementation for the details.

Routing to a subset of hosts

TCP proxy can be configured to route to a subset of hosts within an upstream cluster.

To define metadata that a suitable upstream host must match, use one of the following fields:

  1. Use TcpProxy.metadata_match to define required metadata for a single upstream cluster.

  2. Use ClusterWeight.metadata_match to define required metadata for a weighted upstream cluster.

  3. Use combination of TcpProxy.metadata_match and ClusterWeight.metadata_match to define required metadata for a weighted upstream cluster (metadata from the latter will be merged on top of the former).

Statistics

The TCP proxy filter emits both its own downstream statistics as well as many of the cluster upstream statistics where applicable. The downstream statistics are rooted at tcp.<stat_prefix>. with the following statistics:

Name

Type

Description

downstream_cx_total

Counter

Total number of connections handled by the filter

downstream_cx_no_route

Counter

Number of connections for which no matching route was found or the cluster for the route was not found

downstream_cx_tx_bytes_total

Counter

Total bytes written to the downstream connection

downstream_cx_tx_bytes_buffered

Gauge

Total bytes currently buffered to the downstream connection

downstream_cx_rx_bytes_total

Counter

Total bytes read from the downstream connection

downstream_cx_rx_bytes_buffered

Gauge

Total bytes currently buffered from the downstream connection

downstream_flow_control_paused_reading_total

Counter

Total number of times flow control paused reading from downstream

downstream_flow_control_resumed_reading_total

Counter

Total number of times flow control resumed reading from downstream

idle_timeout

Counter

Total number of connections closed due to idle timeout

upstream_flush_total

Counter

Total number of connections that continued to flush upstream data after the downstream connection was closed

upstream_flush_active

Gauge

Total connections currently continuing to flush upstream data after the downstream connection was closed