luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-consul/command/connect/envoy/testdata/custom-bootstrap.golden

17 lines
262 B
Plaintext
Raw Normal View History

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 14:30:17 +00:00
{
"admin": {
"access_log_path": "/dev/null",
"address": {
"socket_address": {
"address": "127.0.0.1",
"port_value": 19000
}
}
},
"node": {
[OSS] consul connect envoy command changes for agentless (#13361) Changes the sourcing of the envoy bootstrap configuration to not use agent APIs and instead use the catalog(server) API. This is done by passing a node-name flag to the command, (which can only be used with proxy-id). Also fixes a bug where the golden envoy bootstrap config files used for tests did not use the expected destination service name in certain places for connect proxy kind.
2022-06-06 16:23:08 +00:00
"cluster": "test",
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 14:30:17 +00:00
"id": "test-proxy"
},
"custom_field": "foo"
command: when generating envoy bootstrap configs to stdout do not mix informational logs into the json (#9980) Fixes #9921
2021-04-07 19:22:52 +00:00
}