contrib/envoy/extensions/reverse_tunnel_reporters/v3alpha/clients/grpc_client/grpc_client.proto (proto)

extensions.reverse_tunnel_reporters.v3alpha.clients.grpc_client.GrpcClientConfig

[extensions.reverse_tunnel_reporters.v3alpha.clients.grpc_client.GrpcClientConfig proto]

Configuration for gRPC push-based connection event client. Actively pushes connection events to a cluster using grpc using some internal timing.

{
  "stat_prefix": ...,
  "cluster": ...,
  "default_send_interval": {...},
  "connect_retry_interval": {...},
  "max_retries": ...,
  "max_buffer_count": ...
}

stat_prefix: (string) Stat prefix for this client’s metrics.

cluster: (string, REQUIRED) Name of the cluster to send gRPC requests to. It must be present in the config otherwise the setup will throw error in the onServerInitialized.

default_send_interval: (Duration) Default interval between sending batched connection events. Default is 5s.

connect_retry_interval: (Duration) Interval between connection retry attempts to the gRPC service. Connect timeouts are provided at the cluster level and will be handled by the http/2 client. How much time to wait after a failed connect before retrying. Default is 5s.

max_retries: (uint32) Maximum number of retry attempts for failed gRPC sends. Basically the cluster will have default_send_interval * max_retries time to respond. Default is 5. After this we will disconnect and try to connect again.

max_buffer_count: (uint32) Maximum events to buffer at any given time Default is 1,000,000.