91df06098c
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. |
||
---|---|---|
.. | ||
ca | ||
envoy | ||
proxy | ||
connect.go | ||
connect_test.go |