consul/command/connect/envoy
R.B. Boyer 72207256b9
xds: improve how envoy metrics are emitted (#6312)
Since generated envoy clusters all are named using (mostly) SNI syntax
we can have envoy read the various fields out of that structure and emit
it as stats labels to the various telemetry backends.

I changed the delimiter for the 'customization hash' from ':' to '~'
because ':' is always reencoded by envoy as '_' when generating metrics
keys.
2019-08-16 09:30:17 -05:00
..
pipe-bootstrap Fix envoy 1.10 exec (#5964) 2019-06-21 16:06:25 +01:00
testdata xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
bootstrap_config.go xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
bootstrap_config_test.go xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
bootstrap_tpl.go connect: allow overriding envoy listener bind_address (#6033) 2019-07-05 16:06:47 +01:00
envoy.go connect: remove managed proxies (#6220) 2019-08-09 15:19:30 -04:00
envoy_test.go xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
exec_test.go Set --max-obj-name-len 256 when execing Envoy (#6202) 2019-07-26 15:43:15 -04:00
exec_unix.go Set --max-obj-name-len 256 when execing Envoy (#6202) 2019-07-26 15:43:15 -04:00
exec_unsupported.go cli: avoid passing envoy bootstrap configuration as arguments (#4747) 2018-10-10 16:55:34 +01:00