All Downloads are FREE. Search and download functionalities are using the official Maven repository.

io.envoyproxy.envoy.service.load_stats.v3alpha.LoadStatsResponseOrBuilder Maven / Gradle / Ivy

There is a newer version: 1.0.46
Show newest version
// Generated by the protocol buffer compiler.  DO NOT EDIT!
// source: envoy/service/load_stats/v3alpha/lrs.proto

package io.envoyproxy.envoy.service.load_stats.v3alpha;

public interface LoadStatsResponseOrBuilder extends
    // @@protoc_insertion_point(interface_extends:envoy.service.load_stats.v3alpha.LoadStatsResponse)
    com.google.protobuf.MessageOrBuilder {

  /**
   * 
   * Clusters to report stats for.
   * 
* * repeated string clusters = 1 [(.validate.rules) = { ... } */ java.util.List getClustersList(); /** *
   * Clusters to report stats for.
   * 
* * repeated string clusters = 1 [(.validate.rules) = { ... } */ int getClustersCount(); /** *
   * Clusters to report stats for.
   * 
* * repeated string clusters = 1 [(.validate.rules) = { ... } */ java.lang.String getClusters(int index); /** *
   * Clusters to report stats for.
   * 
* * repeated string clusters = 1 [(.validate.rules) = { ... } */ com.google.protobuf.ByteString getClustersBytes(int index); /** *
   * 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.
   * 
* * .google.protobuf.Duration load_reporting_interval = 2; */ boolean hasLoadReportingInterval(); /** *
   * 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.
   * 
* * .google.protobuf.Duration load_reporting_interval = 2; */ com.google.protobuf.Duration getLoadReportingInterval(); /** *
   * 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.
   * 
* * .google.protobuf.Duration load_reporting_interval = 2; */ com.google.protobuf.DurationOrBuilder getLoadReportingIntervalOrBuilder(); /** *
   * Set to *true* if the management server supports endpoint granularity
   * report.
   * 
* * bool report_endpoint_granularity = 3; */ boolean getReportEndpointGranularity(); }




© 2015 - 2024 Weber Informatics LLC | Privacy Policy