AWS SDK for C++
1.9.106
AWS SDK for C++

#include <GetLoadBalancerMetricDataRequest.h>
Additional Inherited Members  
Protected Member Functions inherited from Aws::AmazonWebServiceRequest  
virtual void  DumpBodyToUrl (Aws::Http::URI &uri) const 
Definition at line 26 of file GetLoadBalancerMetricDataRequest.h.
Aws::Lightsail::Model::GetLoadBalancerMetricDataRequest::GetLoadBalancerMetricDataRequest  (  ) 

inline 
The statistic for the metric.
The following statistics are available:
Minimum
 The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.
Maximum
 The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.
Sum
 All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.
Average
 The value of Sum / SampleCount during the specified period. By comparing this statistic with the Minimum and Maximum values, you can determine the full scope of a metric and how close the average use is to the Minimum and Maximum values. This comparison helps you to know when to increase or decrease your resources.
SampleCount
 The count, or number, of data points used for the statistical calculation.
Definition at line 809 of file GetLoadBalancerMetricDataRequest.h.

inline 
The statistic for the metric.
The following statistics are available:
Minimum
 The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.
Maximum
 The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.
Sum
 All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.
Average
 The value of Sum / SampleCount during the specified period. By comparing this statistic with the Minimum and Maximum values, you can determine the full scope of a metric and how close the average use is to the Minimum and Maximum values. This comparison helps you to know when to increase or decrease your resources.
SampleCount
 The count, or number, of data points used for the statistical calculation.
Definition at line 828 of file GetLoadBalancerMetricDataRequest.h.

inline 
The end time of the period.
Definition at line 612 of file GetLoadBalancerMetricDataRequest.h.

inline 
The end time of the period.
Definition at line 607 of file GetLoadBalancerMetricDataRequest.h.

inline 
The name of the load balancer.
Definition at line 45 of file GetLoadBalancerMetricDataRequest.h.

inline 
The metric for which you want to return information.
Valid load balancer metric names are listed below, along with the most useful statistics
to include in your request, and the published unit
value.
ClientTLSNegotiationErrorCount
 The number of TLS connections initiated by the client that did not establish a session with the load balancer due to a TLS error generated by the load balancer. Possible causes include a mismatch of ciphers or protocols.
Statistics
: The most useful statistic is Sum
.
Unit
: The published unit is Count
.
HealthyHostCount
 The number of target instances that are considered healthy.
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
HTTPCode_Instance_2XX_Count
 The number of HTTP 2XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_3XX_Count
 The number of HTTP 3XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_4XX_Count
 The number of HTTP 4XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_5XX_Count
 The number of HTTP 5XX 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
.
Unit
: The published unit is Count
.
HTTPCode_LB_4XX_Count
 The number of HTTP 4XX client error codes that originated from the load balancer. Client errors are generated when requests are malformed or incomplete. These requests were not received by the target instance. This count does not include response codes generated by the target instances.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
HTTPCode_LB_5XX_Count
 The number of HTTP 5XX server error codes that originated from the load balancer. This does not include any response codes generated by the target instance. This metric is reported if there are no healthy instances attached to the load balancer, or if the request rate exceeds the capacity of the instances (spillover) or the load balancer.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Seconds
.
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
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Count
.
UnhealthyHostCount
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
Definition at line 159 of file GetLoadBalancerMetricDataRequest.h.

inline 
The granularity, in seconds, of the returned data points.
Definition at line 555 of file GetLoadBalancerMetricDataRequest.h.

overridevirtual 
Reimplemented from Aws::Lightsail::LightsailRequest.

inlineoverridevirtual 
Implements Aws::AmazonWebServiceRequest.
Definition at line 35 of file GetLoadBalancerMetricDataRequest.h.

inline 
The start time of the period.
Definition at line 576 of file GetLoadBalancerMetricDataRequest.h.

inline 
The statistic for the metric.
The following statistics are available:
Minimum
 The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.
Maximum
 The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.
Sum
 All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.
Average
 The value of Sum / SampleCount during the specified period. By comparing this statistic with the Minimum and Maximum values, you can determine the full scope of a metric and how close the average use is to the Minimum and Maximum values. This comparison helps you to know when to increase or decrease your resources.
SampleCount
 The count, or number, of data points used for the statistical calculation.
Definition at line 695 of file GetLoadBalancerMetricDataRequest.h.

inline 
The unit for the metric data request. Valid units depend on the metric data being requested. For the valid units with each available metric, see the metricName
parameter.
Definition at line 640 of file GetLoadBalancerMetricDataRequest.h.

inline 
The name of the load balancer.
Definition at line 50 of file GetLoadBalancerMetricDataRequest.h.

inline 
The metric for which you want to return information.
Valid load balancer metric names are listed below, along with the most useful statistics
to include in your request, and the published unit
value.
ClientTLSNegotiationErrorCount
 The number of TLS connections initiated by the client that did not establish a session with the load balancer due to a TLS error generated by the load balancer. Possible causes include a mismatch of ciphers or protocols.
Statistics
: The most useful statistic is Sum
.
Unit
: The published unit is Count
.
HealthyHostCount
 The number of target instances that are considered healthy.
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
HTTPCode_Instance_2XX_Count
 The number of HTTP 2XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_3XX_Count
 The number of HTTP 3XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_4XX_Count
 The number of HTTP 4XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_5XX_Count
 The number of HTTP 5XX 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
.
Unit
: The published unit is Count
.
HTTPCode_LB_4XX_Count
 The number of HTTP 4XX client error codes that originated from the load balancer. Client errors are generated when requests are malformed or incomplete. These requests were not received by the target instance. This count does not include response codes generated by the target instances.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
HTTPCode_LB_5XX_Count
 The number of HTTP 5XX server error codes that originated from the load balancer. This does not include any response codes generated by the target instance. This metric is reported if there are no healthy instances attached to the load balancer, or if the request rate exceeds the capacity of the instances (spillover) or the load balancer.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Seconds
.
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
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Count
.
UnhealthyHostCount
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
Definition at line 237 of file GetLoadBalancerMetricDataRequest.h.

inline 
The granularity, in seconds, of the returned data points.
Definition at line 560 of file GetLoadBalancerMetricDataRequest.h.

overridevirtual 
Convert payload into String.
Implements Aws::AmazonSerializableWebServiceRequest.

inline 
The end time of the period.
Definition at line 622 of file GetLoadBalancerMetricDataRequest.h.

inline 
The end time of the period.
Definition at line 617 of file GetLoadBalancerMetricDataRequest.h.

inline 
The name of the load balancer.
Definition at line 60 of file GetLoadBalancerMetricDataRequest.h.

inline 
The name of the load balancer.
Definition at line 55 of file GetLoadBalancerMetricDataRequest.h.

inline 
The name of the load balancer.
Definition at line 65 of file GetLoadBalancerMetricDataRequest.h.

inline 
The metric for which you want to return information.
Valid load balancer metric names are listed below, along with the most useful statistics
to include in your request, and the published unit
value.
ClientTLSNegotiationErrorCount
 The number of TLS connections initiated by the client that did not establish a session with the load balancer due to a TLS error generated by the load balancer. Possible causes include a mismatch of ciphers or protocols.
Statistics
: The most useful statistic is Sum
.
Unit
: The published unit is Count
.
HealthyHostCount
 The number of target instances that are considered healthy.
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
HTTPCode_Instance_2XX_Count
 The number of HTTP 2XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_3XX_Count
 The number of HTTP 3XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_4XX_Count
 The number of HTTP 4XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_5XX_Count
 The number of HTTP 5XX 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
.
Unit
: The published unit is Count
.
HTTPCode_LB_4XX_Count
 The number of HTTP 4XX client error codes that originated from the load balancer. Client errors are generated when requests are malformed or incomplete. These requests were not received by the target instance. This count does not include response codes generated by the target instances.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
HTTPCode_LB_5XX_Count
 The number of HTTP 5XX server error codes that originated from the load balancer. This does not include any response codes generated by the target instance. This metric is reported if there are no healthy instances attached to the load balancer, or if the request rate exceeds the capacity of the instances (spillover) or the load balancer.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Seconds
.
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
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Count
.
UnhealthyHostCount
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
Definition at line 315 of file GetLoadBalancerMetricDataRequest.h.

inline 
The metric for which you want to return information.
Valid load balancer metric names are listed below, along with the most useful statistics
to include in your request, and the published unit
value.
ClientTLSNegotiationErrorCount
 The number of TLS connections initiated by the client that did not establish a session with the load balancer due to a TLS error generated by the load balancer. Possible causes include a mismatch of ciphers or protocols.
Statistics
: The most useful statistic is Sum
.
Unit
: The published unit is Count
.
HealthyHostCount
 The number of target instances that are considered healthy.
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
HTTPCode_Instance_2XX_Count
 The number of HTTP 2XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_3XX_Count
 The number of HTTP 3XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_4XX_Count
 The number of HTTP 4XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_5XX_Count
 The number of HTTP 5XX 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
.
Unit
: The published unit is Count
.
HTTPCode_LB_4XX_Count
 The number of HTTP 4XX client error codes that originated from the load balancer. Client errors are generated when requests are malformed or incomplete. These requests were not received by the target instance. This count does not include response codes generated by the target instances.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
HTTPCode_LB_5XX_Count
 The number of HTTP 5XX server error codes that originated from the load balancer. This does not include any response codes generated by the target instance. This metric is reported if there are no healthy instances attached to the load balancer, or if the request rate exceeds the capacity of the instances (spillover) or the load balancer.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Seconds
.
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
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Count
.
UnhealthyHostCount
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
Definition at line 393 of file GetLoadBalancerMetricDataRequest.h.

inline 
The granularity, in seconds, of the returned data points.
Definition at line 565 of file GetLoadBalancerMetricDataRequest.h.

inline 
The start time of the period.
Definition at line 591 of file GetLoadBalancerMetricDataRequest.h.

inline 
The start time of the period.
Definition at line 586 of file GetLoadBalancerMetricDataRequest.h.

inline 
The statistic for the metric.
The following statistics are available:
Minimum
 The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.
Maximum
 The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.
Sum
 All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.
Average
 The value of Sum / SampleCount during the specified period. By comparing this statistic with the Minimum and Maximum values, you can determine the full scope of a metric and how close the average use is to the Minimum and Maximum values. This comparison helps you to know when to increase or decrease your resources.
SampleCount
 The count, or number, of data points used for the statistical calculation.
Definition at line 752 of file GetLoadBalancerMetricDataRequest.h.

inline 
The statistic for the metric.
The following statistics are available:
Minimum
 The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.
Maximum
 The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.
Sum
 All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.
Average
 The value of Sum / SampleCount during the specified period. By comparing this statistic with the Minimum and Maximum values, you can determine the full scope of a metric and how close the average use is to the Minimum and Maximum values. This comparison helps you to know when to increase or decrease your resources.
SampleCount
 The count, or number, of data points used for the statistical calculation.
Definition at line 733 of file GetLoadBalancerMetricDataRequest.h.

inline 
The unit for the metric data request. Valid units depend on the metric data being requested. For the valid units with each available metric, see the metricName
parameter.
Definition at line 654 of file GetLoadBalancerMetricDataRequest.h.

inline 
The unit for the metric data request. Valid units depend on the metric data being requested. For the valid units with each available metric, see the metricName
parameter.
Definition at line 661 of file GetLoadBalancerMetricDataRequest.h.

inline 
The start time of the period.
Definition at line 581 of file GetLoadBalancerMetricDataRequest.h.

inline 
The statistic for the metric.
The following statistics are available:
Minimum
 The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.
Maximum
 The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.
Sum
 All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.
Average
 The value of Sum / SampleCount during the specified period. By comparing this statistic with the Minimum and Maximum values, you can determine the full scope of a metric and how close the average use is to the Minimum and Maximum values. This comparison helps you to know when to increase or decrease your resources.
SampleCount
 The count, or number, of data points used for the statistical calculation.
Definition at line 714 of file GetLoadBalancerMetricDataRequest.h.

inline 
The unit for the metric data request. Valid units depend on the metric data being requested. For the valid units with each available metric, see the metricName
parameter.
Definition at line 647 of file GetLoadBalancerMetricDataRequest.h.

inline 
The end time of the period.
Definition at line 632 of file GetLoadBalancerMetricDataRequest.h.

inline 
The end time of the period.
Definition at line 627 of file GetLoadBalancerMetricDataRequest.h.

inline 
The name of the load balancer.
Definition at line 75 of file GetLoadBalancerMetricDataRequest.h.

inline 
The name of the load balancer.
Definition at line 70 of file GetLoadBalancerMetricDataRequest.h.

inline 
The name of the load balancer.
Definition at line 80 of file GetLoadBalancerMetricDataRequest.h.

inline 
The metric for which you want to return information.
Valid load balancer metric names are listed below, along with the most useful statistics
to include in your request, and the published unit
value.
ClientTLSNegotiationErrorCount
 The number of TLS connections initiated by the client that did not establish a session with the load balancer due to a TLS error generated by the load balancer. Possible causes include a mismatch of ciphers or protocols.
Statistics
: The most useful statistic is Sum
.
Unit
: The published unit is Count
.
HealthyHostCount
 The number of target instances that are considered healthy.
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
HTTPCode_Instance_2XX_Count
 The number of HTTP 2XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_3XX_Count
 The number of HTTP 3XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_4XX_Count
 The number of HTTP 4XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_5XX_Count
 The number of HTTP 5XX 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
.
Unit
: The published unit is Count
.
HTTPCode_LB_4XX_Count
 The number of HTTP 4XX client error codes that originated from the load balancer. Client errors are generated when requests are malformed or incomplete. These requests were not received by the target instance. This count does not include response codes generated by the target instances.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
HTTPCode_LB_5XX_Count
 The number of HTTP 5XX server error codes that originated from the load balancer. This does not include any response codes generated by the target instance. This metric is reported if there are no healthy instances attached to the load balancer, or if the request rate exceeds the capacity of the instances (spillover) or the load balancer.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Seconds
.
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
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Count
.
UnhealthyHostCount
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
Definition at line 471 of file GetLoadBalancerMetricDataRequest.h.

inline 
The metric for which you want to return information.
Valid load balancer metric names are listed below, along with the most useful statistics
to include in your request, and the published unit
value.
ClientTLSNegotiationErrorCount
 The number of TLS connections initiated by the client that did not establish a session with the load balancer due to a TLS error generated by the load balancer. Possible causes include a mismatch of ciphers or protocols.
Statistics
: The most useful statistic is Sum
.
Unit
: The published unit is Count
.
HealthyHostCount
 The number of target instances that are considered healthy.
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
HTTPCode_Instance_2XX_Count
 The number of HTTP 2XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_3XX_Count
 The number of HTTP 3XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_4XX_Count
 The number of HTTP 4XX 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
.
Unit
: The published unit is Count
.
HTTPCode_Instance_5XX_Count
 The number of HTTP 5XX 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
.
Unit
: The published unit is Count
.
HTTPCode_LB_4XX_Count
 The number of HTTP 4XX client error codes that originated from the load balancer. Client errors are generated when requests are malformed or incomplete. These requests were not received by the target instance. This count does not include response codes generated by the target instances.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
HTTPCode_LB_5XX_Count
 The number of HTTP 5XX server error codes that originated from the load balancer. This does not include any response codes generated by the target instance. This metric is reported if there are no healthy instances attached to the load balancer, or if the request rate exceeds the capacity of the instances (spillover) or the load balancer.
Statistics
: The most useful statistic is Sum
. Note that Minimum
, Maximum
, and Average
all return 1
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Seconds
.
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
.
Unit
: The published unit is Count
.
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
.
Unit
: The published unit is Count
.
UnhealthyHostCount
Statistics
: The most useful statistic are Average
, Minimum
, and Maximum
.
Unit
: The published unit is Count
.
Definition at line 549 of file GetLoadBalancerMetricDataRequest.h.

inline 
The granularity, in seconds, of the returned data points.
Definition at line 570 of file GetLoadBalancerMetricDataRequest.h.

inline 
The start time of the period.
Definition at line 601 of file GetLoadBalancerMetricDataRequest.h.

inline 
The start time of the period.
Definition at line 596 of file GetLoadBalancerMetricDataRequest.h.

inline 
The statistic for the metric.
The following statistics are available:
Minimum
 The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.
Maximum
 The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.
Sum
 All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.
Average
 The value of Sum / SampleCount during the specified period. By comparing this statistic with the Minimum and Maximum values, you can determine the full scope of a metric and how close the average use is to the Minimum and Maximum values. This comparison helps you to know when to increase or decrease your resources.
SampleCount
 The count, or number, of data points used for the statistical calculation.
Definition at line 790 of file GetLoadBalancerMetricDataRequest.h.

inline 
The statistic for the metric.
The following statistics are available:
Minimum
 The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.
Maximum
 The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.
Sum
 All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.
Average
 The value of Sum / SampleCount during the specified period. By comparing this statistic with the Minimum and Maximum values, you can determine the full scope of a metric and how close the average use is to the Minimum and Maximum values. This comparison helps you to know when to increase or decrease your resources.
SampleCount
 The count, or number, of data points used for the statistical calculation.
Definition at line 771 of file GetLoadBalancerMetricDataRequest.h.

inline 
The unit for the metric data request. Valid units depend on the metric data being requested. For the valid units with each available metric, see the metricName
parameter.
Definition at line 668 of file GetLoadBalancerMetricDataRequest.h.

inline 
The unit for the metric data request. Valid units depend on the metric data being requested. For the valid units with each available metric, see the metricName
parameter.
Definition at line 675 of file GetLoadBalancerMetricDataRequest.h.