@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class GetLoadBalancerMetricDataRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
NOOP| Constructor and Description |
|---|
GetLoadBalancerMetricDataRequest() |
| Modifier and Type | Method and Description |
|---|---|
GetLoadBalancerMetricDataRequest |
clone()
Creates a shallow clone of this object for all fields except the handler context.
|
boolean |
equals(Object obj) |
Date |
getEndTime()
The end time of the period.
|
String |
getLoadBalancerName()
The name of the load balancer.
|
String |
getMetricName()
The metric for which you want to return information.
|
Integer |
getPeriod()
The granularity, in seconds, of the returned data points.
|
Date |
getStartTime()
The start time of the period.
|
List<String> |
getStatistics()
The statistic for the metric.
|
String |
getUnit()
The unit for the metric data request.
|
int |
hashCode() |
void |
setEndTime(Date endTime)
The end time of the period.
|
void |
setLoadBalancerName(String loadBalancerName)
The name of the load balancer.
|
void |
setMetricName(String metricName)
The metric for which you want to return information.
|
void |
setPeriod(Integer period)
The granularity, in seconds, of the returned data points.
|
void |
setStartTime(Date startTime)
The start time of the period.
|
void |
setStatistics(Collection<String> statistics)
The statistic for the metric.
|
void |
setUnit(String unit)
The unit for the metric data request.
|
String |
toString()
Returns a string representation of this object.
|
GetLoadBalancerMetricDataRequest |
withEndTime(Date endTime)
The end time of the period.
|
GetLoadBalancerMetricDataRequest |
withLoadBalancerName(String loadBalancerName)
The name of the load balancer.
|
GetLoadBalancerMetricDataRequest |
withMetricName(LoadBalancerMetricName metricName)
The metric for which you want to return information.
|
GetLoadBalancerMetricDataRequest |
withMetricName(String metricName)
The metric for which you want to return information.
|
GetLoadBalancerMetricDataRequest |
withPeriod(Integer period)
The granularity, in seconds, of the returned data points.
|
GetLoadBalancerMetricDataRequest |
withStartTime(Date startTime)
The start time of the period.
|
GetLoadBalancerMetricDataRequest |
withStatistics(Collection<String> statistics)
The statistic for the metric.
|
GetLoadBalancerMetricDataRequest |
withStatistics(MetricStatistic... statistics)
The statistic for the metric.
|
GetLoadBalancerMetricDataRequest |
withStatistics(String... statistics)
The statistic for the metric.
|
GetLoadBalancerMetricDataRequest |
withUnit(MetricUnit unit)
The unit for the metric data request.
|
GetLoadBalancerMetricDataRequest |
withUnit(String unit)
The unit for the metric data request.
|
addHandlerContext, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getHandlerContext, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestCredentialsProvider, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestCredentialsProvider, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestCredentialsProvider, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeoutpublic void setLoadBalancerName(String loadBalancerName)
The name of the load balancer.
loadBalancerName - The name of the load balancer.public String getLoadBalancerName()
The name of the load balancer.
public GetLoadBalancerMetricDataRequest withLoadBalancerName(String loadBalancerName)
The name of the load balancer.
loadBalancerName - The name of the load balancer.public void setMetricName(String metricName)
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 - The number of target instances that are considered unhealthy.
Statistics: The most useful statistic are Average, Minimum, and
Maximum.
Unit: The published unit is Count.
metricName - 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 - The number of target instances that are considered unhealthy.
Statistics: The most useful statistic are Average, Minimum, and
Maximum.
Unit: The published unit is Count.
LoadBalancerMetricNamepublic String getMetricName()
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 - The number of target instances that are considered unhealthy.
Statistics: The most useful statistic are Average, Minimum, and
Maximum.
Unit: The published unit is Count.
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 - The number of target instances that are considered unhealthy.
Statistics: The most useful statistic are Average, Minimum, and
Maximum.
Unit: The published unit is Count.
LoadBalancerMetricNamepublic GetLoadBalancerMetricDataRequest withMetricName(String metricName)
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 - The number of target instances that are considered unhealthy.
Statistics: The most useful statistic are Average, Minimum, and
Maximum.
Unit: The published unit is Count.
metricName - 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 - The number of target instances that are considered unhealthy.
Statistics: The most useful statistic are Average, Minimum, and
Maximum.
Unit: The published unit is Count.
LoadBalancerMetricNamepublic GetLoadBalancerMetricDataRequest withMetricName(LoadBalancerMetricName metricName)
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 - The number of target instances that are considered unhealthy.
Statistics: The most useful statistic are Average, Minimum, and
Maximum.
Unit: The published unit is Count.
metricName - 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 - The number of target instances that are considered unhealthy.
Statistics: The most useful statistic are Average, Minimum, and
Maximum.
Unit: The published unit is Count.
LoadBalancerMetricNamepublic void setPeriod(Integer period)
The granularity, in seconds, of the returned data points.
period - The granularity, in seconds, of the returned data points.public Integer getPeriod()
The granularity, in seconds, of the returned data points.
public GetLoadBalancerMetricDataRequest withPeriod(Integer period)
The granularity, in seconds, of the returned data points.
period - The granularity, in seconds, of the returned data points.public void setStartTime(Date startTime)
The start time of the period.
startTime - The start time of the period.public Date getStartTime()
The start time of the period.
public GetLoadBalancerMetricDataRequest withStartTime(Date startTime)
The start time of the period.
startTime - The start time of the period.public void setEndTime(Date endTime)
The end time of the period.
endTime - The end time of the period.public Date getEndTime()
The end time of the period.
public GetLoadBalancerMetricDataRequest withEndTime(Date endTime)
The end time of the period.
endTime - The end time of the period.public void setUnit(String unit)
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.
unit - 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.MetricUnitpublic String getUnit()
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.
metricName parameter.MetricUnitpublic GetLoadBalancerMetricDataRequest withUnit(String unit)
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.
unit - 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.MetricUnitpublic GetLoadBalancerMetricDataRequest withUnit(MetricUnit unit)
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.
unit - 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.MetricUnitpublic List<String> getStatistics()
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.
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.
MetricStatisticpublic void setStatistics(Collection<String> statistics)
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.
statistics - 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.
MetricStatisticpublic GetLoadBalancerMetricDataRequest withStatistics(String... statistics)
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.
NOTE: This method appends the values to the existing list (if any). Use
setStatistics(java.util.Collection) or withStatistics(java.util.Collection) if you want to
override the existing values.
statistics - 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.
MetricStatisticpublic GetLoadBalancerMetricDataRequest withStatistics(Collection<String> statistics)
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.
statistics - 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.
MetricStatisticpublic GetLoadBalancerMetricDataRequest withStatistics(MetricStatistic... statistics)
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.
statistics - 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.
MetricStatisticpublic String toString()
toString in class ObjectObject.toString()public GetLoadBalancerMetricDataRequest clone()
AmazonWebServiceRequestclone in class AmazonWebServiceRequestObject.clone()