envoyproxy/envoy

UDP cluster support for statsd addresses

Open

#1,028 opened on May 30, 2017

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

Repository metrics

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

Description

From @jylin in https://github.com/lyft/envoy/pull/1019:

Would it make sense to try to make the "statsd_tcp_cluster_name" then support UDP too (i.e. a "statsd_udp_cluster_name")?

(in reference to avoiding hardcoding IP addresses in config files for statsd)

This seems reasonable from a config/API perspective, but will involve a bit of work to make work. Currently the cluster implementations such as LogicalDnsCluster are assuming TCP connections.

This is also related to #492 - if there was general support for UDP proxying we would be able to leverage that to do have UDP addressable clusters for statsd.

Contributor guide

Research direction
Examine LogicalDnsCluster and other cluster implementations to understand how they assume TCP; design a way to support UDP for statsd addresses.
Tech stack
cpp
Domain
networkingbackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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.
Mostly clear
Prerequisites
GitC++Envoy clustering concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35