com.amazonaws.services.lightsail.model

Class GetLoadBalancerMetricDataResult

java.lang.Object

com.amazonaws.AmazonWebServiceResult<ResponseMetadata>

com.amazonaws.services.lightsail.model.GetLoadBalancerMetricDataResult

All Implemented Interfaces:

Serializable, Cloneable

@Generated(value="com.amazonaws:aws-java-sdk-code-generator")
public class GetLoadBalancerMetricDataResult
extends AmazonWebServiceResult<ResponseMetadata>
implements Serializable, Cloneable

See Also:

AWS API Documentation, Serialized Form

Constructor Summary

Constructors

Constructor and Description
GetLoadBalancerMetricDataResult()

Method Summary

Modifier and Type	Method and Description
GetLoadBalancerMetricDataResult	clone()
boolean	equals(Object obj)
List<MetricDatapoint>	getMetricData() An array of metric datapoint objects.
String	getMetricName() The metric about which you are receiving information.
int	hashCode()
void	setMetricData(Collection<MetricDatapoint> metricData) An array of metric datapoint objects.
void	setMetricName(String metricName) The metric about which you are receiving information.
String	toString() Returns a string representation of this object; useful for testing and debugging.
GetLoadBalancerMetricDataResult	withMetricData(Collection<MetricDatapoint> metricData) An array of metric datapoint objects.
GetLoadBalancerMetricDataResult	withMetricData(MetricDatapoint... metricData) An array of metric datapoint objects.
GetLoadBalancerMetricDataResult	withMetricName(LoadBalancerMetricName metricName) The metric about which you are receiving information.
GetLoadBalancerMetricDataResult	withMetricName(String metricName) The metric about which you are receiving information.

Methods inherited from class com.amazonaws.AmazonWebServiceResult

getSdkHttpMetadata, getSdkResponseMetadata, setSdkHttpMetadata, setSdkResponseMetadata

Methods inherited from class java.lang.Object

getClass, notify, notifyAll, wait, wait, wait

Constructor Detail

GetLoadBalancerMetricDataResult

public GetLoadBalancerMetricDataResult()

Method Detail

setMetricName

public void setMetricName(String metricName)

The metric about which you are receiving 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.

• HTTPCode_LB_4XX_Count - 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.

• HTTPCode_LB_5XX_Count - 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.

• HTTPCode_Instance_2XX_Count - 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.

• HTTPCode_Instance_3XX_Count - 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.

• HTTPCode_Instance_4XX_Count - 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.

• HTTPCode_Instance_5XX_Count - 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.

Parameters:

metricName - The metric about which you are receiving 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.

• HTTPCode_LB_4XX_Count - 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.

• HTTPCode_LB_5XX_Count - 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.

• HTTPCode_Instance_2XX_Count - 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.

• HTTPCode_Instance_3XX_Count - 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.

• HTTPCode_Instance_4XX_Count - 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.

• HTTPCode_Instance_5XX_Count - 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.

See Also:

LoadBalancerMetricName

getMetricName

public String getMetricName()

The metric about which you are receiving 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.

• HTTPCode_LB_4XX_Count - 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.

• HTTPCode_LB_5XX_Count - 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.

• HTTPCode_Instance_2XX_Count - 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.

• HTTPCode_Instance_3XX_Count - 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.

• HTTPCode_Instance_4XX_Count - 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.

• HTTPCode_Instance_5XX_Count - 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.

Returns:

The metric about which you are receiving 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.

• HTTPCode_LB_4XX_Count - 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.

• HTTPCode_LB_5XX_Count - 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.

• HTTPCode_Instance_2XX_Count - 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.

• HTTPCode_Instance_3XX_Count - 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.

• HTTPCode_Instance_4XX_Count - 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.

• HTTPCode_Instance_5XX_Count - 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.

See Also:

LoadBalancerMetricName

withMetricName

public GetLoadBalancerMetricDataResult withMetricName(String metricName)

The metric about which you are receiving 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.

• HTTPCode_LB_4XX_Count - 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.

• HTTPCode_LB_5XX_Count - 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.

• HTTPCode_Instance_2XX_Count - 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.

• HTTPCode_Instance_3XX_Count - 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.

• HTTPCode_Instance_4XX_Count - 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.

• HTTPCode_Instance_5XX_Count - 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.

Parameters:

metricName - The metric about which you are receiving 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.

• HTTPCode_LB_4XX_Count - 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.

• HTTPCode_LB_5XX_Count - 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.

• HTTPCode_Instance_2XX_Count - 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.

• HTTPCode_Instance_3XX_Count - 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.

• HTTPCode_Instance_4XX_Count - 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.

• HTTPCode_Instance_5XX_Count - 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.

Returns:

Returns a reference to this object so that method calls can be chained together.

See Also:

LoadBalancerMetricName

withMetricName

public GetLoadBalancerMetricDataResult withMetricName(LoadBalancerMetricName metricName)

The metric about which you are receiving 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.

• HTTPCode_LB_4XX_Count - 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.

• HTTPCode_LB_5XX_Count - 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.

• HTTPCode_Instance_2XX_Count - 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.

• HTTPCode_Instance_3XX_Count - 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.

• HTTPCode_Instance_4XX_Count - 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.

• HTTPCode_Instance_5XX_Count - 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.

Parameters:

metricName - The metric about which you are receiving 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.

• HTTPCode_LB_4XX_Count - 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.

• HTTPCode_LB_5XX_Count - 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.

• HTTPCode_Instance_2XX_Count - 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.

• HTTPCode_Instance_3XX_Count - 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.

• HTTPCode_Instance_4XX_Count - 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.

• HTTPCode_Instance_5XX_Count - 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.

Returns:

Returns a reference to this object so that method calls can be chained together.

See Also:

LoadBalancerMetricName

getMetricData

public List<MetricDatapoint> getMetricData()

An array of metric datapoint objects.

Returns:

An array of metric datapoint objects.

setMetricData

public void setMetricData(Collection<MetricDatapoint> metricData)

An array of metric datapoint objects.

Parameters:

metricData - An array of metric datapoint objects.

withMetricData

public GetLoadBalancerMetricDataResult withMetricData(MetricDatapoint... metricData)

An array of metric datapoint objects.

NOTE: This method appends the values to the existing list (if any). Use setMetricData(java.util.Collection) or withMetricData(java.util.Collection) if you want to override the existing values.

Parameters:

metricData - An array of metric datapoint objects.

Returns:

Returns a reference to this object so that method calls can be chained together.

withMetricData

public GetLoadBalancerMetricDataResult withMetricData(Collection<MetricDatapoint> metricData)

An array of metric datapoint objects.

Parameters:

metricData - An array of metric datapoint objects.

Returns:

Returns a reference to this object so that method calls can be chained together.

toString

public String toString()

Returns a string representation of this object; useful for testing and debugging.

Overrides:

toString in class Object

Returns:

A string representation of this object.

See Also:

Object.toString()

equals

public boolean equals(Object obj)

Overrides:

equals in class Object

hashCode

public int hashCode()

Overrides:

hashCode in class Object

clone

public GetLoadBalancerMetricDataResult clone()

Overrides:

clone in class Object