Open johnharris85 opened 1 year ago
Triage: We can potentially put it in a new MeshTrafficMetrics policy #5708
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
@johnharris85 how DownstreamTlsContext
and UpstreamTlsContext
are connected with metrics? Don't we already publish this metrics?
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
Description
We should be able to gather metrics on how the underlying network is performing to understand how this is impacting requests in our mesh gateway.
We would like the statistics listed here: https://www.envoyproxy.io/docs/envoy/latest/configuration/upstream/cluster_manager/cluster_stats#tcp-statistics exposed for both upstreams and downstreams by optionally wrapping the DownstreamTlsContext and UpstreamTlsContext definitions. This only works on Linux so this would likely need to be customisable via a MeshGatewayInstance policy.
For example for a downstream socket: