diff options
Diffstat (limited to 'src/rpc/envoy.service.load_stats.v3.rs')
| -rw-r--r-- | src/rpc/envoy.service.load_stats.v3.rs | 44 |
1 files changed, 0 insertions, 44 deletions
diff --git a/src/rpc/envoy.service.load_stats.v3.rs b/src/rpc/envoy.service.load_stats.v3.rs deleted file mode 100644 index c94f5697..00000000 --- a/src/rpc/envoy.service.load_stats.v3.rs +++ /dev/null @@ -1,44 +0,0 @@ -// @generated -// This file is @generated by prost-build. -/// A load report Envoy sends to the management server. -#[allow(clippy::derive_partial_eq_without_eq)] -#[derive(Clone, PartialEq, ::prost::Message)] -pub struct LoadStatsRequest { - /// Node identifier for Envoy instance. - #[prost(message, optional, tag="1")] - pub node: ::core::option::Option<super::super::super::config::core::v3::Node>, - /// A list of load stats to report. - #[prost(message, repeated, tag="2")] - pub cluster_stats: ::prost::alloc::vec::Vec<super::super::super::config::endpoint::v3::ClusterStats>, -} -/// The management server sends envoy a LoadStatsResponse with all clusters it -/// is interested in learning load stats about. -#[allow(clippy::derive_partial_eq_without_eq)] -#[derive(Clone, PartialEq, ::prost::Message)] -pub struct LoadStatsResponse { - /// Clusters to report stats for. - /// Not populated if ``send_all_clusters`` is true. - #[prost(string, repeated, tag="1")] - pub clusters: ::prost::alloc::vec::Vec<::prost::alloc::string::String>, - /// If true, the client should send all clusters it knows about. - /// Only clients that advertise the "envoy.lrs.supports_send_all_clusters" capability in their - /// :ref:`client_features<envoy_v3_api_field_config.core.v3.Node.client_features>` field will honor this field. - #[prost(bool, tag="4")] - pub send_all_clusters: bool, - /// The minimum interval of time to collect stats over. This is only a minimum for two reasons: - /// - /// 1. There may be some delay from when the timer fires until stats sampling occurs. - /// 2. For clusters that were already feature in the previous ``LoadStatsResponse``, any traffic - /// that is observed in between the corresponding previous ``LoadStatsRequest`` and this - /// ``LoadStatsResponse`` will also be accumulated and billed to the cluster. This avoids a period - /// of inobservability that might otherwise exists between the messages. New clusters are not - /// subject to this consideration. - #[prost(message, optional, tag="2")] - pub load_reporting_interval: ::core::option::Option<super::super::super::super::google::protobuf::Duration>, - /// Set to ``true`` if the management server supports endpoint granularity - /// report. - #[prost(bool, tag="3")] - pub report_endpoint_granularity: bool, -} -include!("envoy.service.load_stats.v3.tonic.rs"); -// @@protoc_insertion_point(module)
\ No newline at end of file |
