Struct rusoto_lightsail::GetLoadBalancerMetricDataRequest

pub struct GetLoadBalancerMetricDataRequest {
    pub end_time: f64,
    pub load_balancer_name: String,
    pub metric_name: String,
    pub period: i64,
    pub start_time: f64,
    pub statistics: Vec<String>,
    pub unit: String,
}

Fields

end_time: f64

The end time of the period.

load_balancer_name: String

The name of the load balancer.

metric_name: String

The metric about which you want to return information. Valid values are listed below, along with the most useful statistics to include in your request.

• ClientTLSNegotiationErrorCount - The number of TLS connections initiated by the client that did not establish a session with the load balancer. Possible causes include a mismatch of ciphers or protocols.

  Statistics: The most useful statistic is Sum.

• HealthyHostCount - The number of target instances that are considered healthy.

  Statistics: The most useful statistic are Average, Minimum, and Maximum.

• UnhealthyHostCount - The number of target instances that are considered unhealthy.

  Statistics: The most useful statistic are Average, Minimum, and Maximum.

• HTTPCodeLB4XXCount - The number of HTTP 4XX client error codes that originate from the load balancer. Client errors are generated when requests are malformed or incomplete. These requests have not been received by the target instance. This count does not include any response codes generated by the target instances.

  Statistics: The most useful statistic is Sum. Note that Minimum, Maximum, and Average all return 1.

• HTTPCodeLB5XXCount - The number of HTTP 5XX server error codes that originate from the load balancer. This count does not include any response codes generated by the target instances.

  Statistics: The most useful statistic is Sum. Note that Minimum, Maximum, and Average all return 1. Note that Minimum, Maximum, and Average all return 1.

• HTTPCodeInstance2XXCount - The number of HTTP response codes generated by the target instances. This does not include any response codes generated by the load balancer.

  Statistics: The most useful statistic is Sum. Note that Minimum, Maximum, and Average all return 1.

• HTTPCodeInstance3XXCount - The number of HTTP response codes generated by the target instances. This does not include any response codes generated by the load balancer.

  Statistics: The most useful statistic is Sum. Note that Minimum, Maximum, and Average all return 1.

• HTTPCodeInstance4XXCount - The number of HTTP response codes generated by the target instances. This does not include any response codes generated by the load balancer.

  Statistics: The most useful statistic is Sum. Note that Minimum, Maximum, and Average all return 1.

• HTTPCodeInstance5XXCount - The number of HTTP response codes generated by the target instances. This does not include any response codes generated by the load balancer.

  Statistics: The most useful statistic is Sum. Note that Minimum, Maximum, and Average all return 1.

• InstanceResponseTime - The time elapsed, in seconds, after the request leaves the load balancer until a response from the target instance is received.

  Statistics: The most useful statistic is Average.

• RejectedConnectionCount - The number of connections that were rejected because the load balancer had reached its maximum number of connections.

  Statistics: The most useful statistic is Sum.

• RequestCount - The number of requests processed over IPv4. This count includes only the requests with a response generated by a target instance of the load balancer.

  Statistics: The most useful statistic is Sum. Note that Minimum, Maximum, and Average all return 1.

period: i64

The granularity, in seconds, of the returned data points.

start_time: f64

The start time of the period.

statistics: Vec<String>

An array of statistics that you want to request metrics for. Valid values are listed below.

• SampleCount - The count (number) of data points used for the statistical calculation.

• Average - The value of Sum / SampleCount during the specified period. By comparing this statistic with the Minimum and Maximum, you can determine the full scope of a metric and how close the average use is to the Minimum and Maximum. This comparison helps you to know when to increase or decrease your resources as needed.

• Sum - All values submitted for the matching metric added together. This statistic can be useful for determining the total volume of a metric.

• Minimum - The lowest value observed during the specified period. You can use this value to determine low volumes of activity for your application.

• Maximum - The highest value observed during the specified period. You can use this value to determine high volumes of activity for your application.

unit: String

The unit for the time period request. Valid values are listed below.

Trait Implementations

impl PartialEq<GetLoadBalancerMetricDataRequest> for GetLoadBalancerMetricDataRequest

fn eq(&self, other: &GetLoadBalancerMetricDataRequest) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &GetLoadBalancerMetricDataRequest) -> bool

This method tests for !=.

impl Default for GetLoadBalancerMetricDataRequest

fn default() -> GetLoadBalancerMetricDataRequest

Returns the "default value" for a type.

impl Clone for GetLoadBalancerMetricDataRequest

fn clone(&self) -> GetLoadBalancerMetricDataRequest

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for GetLoadBalancerMetricDataRequest

fn fmt(&self, f: &mut Formatter) -> Result

Formats the value using the given formatter.

impl Serialize for GetLoadBalancerMetricDataRequest

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error> where
    __S: Serializer, 

Serialize this value into the given Serde serializer.