consul/agent/proxycfg
Freddy 19f6e1ca31
Log the correlation ID when blocking queries fire (#10689)
Knowing that blocking queries are firing does not provide much
information on its own. If we know the correlation IDs we can
piece together which parts of the snapshot have been populated.

Some of these responses might be empty from the blocking
query timing out. But if they're returning quickly I think we
can reasonably assume they contain data.
2021-07-23 16:36:17 -06:00
..
connect_proxy.go agent/structs: add a bunch more EnterpriseMeta helper functions to help with partitioning (#10669) 2021-07-22 13:20:45 -05:00
ingress_gateway.go proxycfg: move each handler into a seprate file 2021-06-21 15:48:40 -04:00
manager.go agent/structs: add a bunch more EnterpriseMeta helper functions to help with partitioning (#10669) 2021-07-22 13:20:45 -05:00
manager_test.go agent/structs: add a bunch more EnterpriseMeta helper functions to help with partitioning (#10669) 2021-07-22 13:20:45 -05:00
mesh_gateway.go agent/structs: add a bunch more EnterpriseMeta helper functions to help with partitioning (#10669) 2021-07-22 13:20:45 -05:00
proxycfg.go
snapshot.go Validate SANs for passthrough clusters and failovers 2021-07-14 22:21:55 -06:00
state.go Log the correlation ID when blocking queries fire (#10689) 2021-07-23 16:36:17 -06:00
state_test.go agent/structs: add a bunch more EnterpriseMeta helper functions to help with partitioning (#10669) 2021-07-22 13:20:45 -05:00
terminating_gateway.go proxycfg: move each handler into a seprate file 2021-06-21 15:48:40 -04:00
testing.go Add tests for xds/listeners 2021-05-04 12:41:43 -07:00
upstreams.go agent/structs: add a bunch more EnterpriseMeta helper functions to help with partitioning (#10669) 2021-07-22 13:20:45 -05:00