// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
pub use crate::operation::get_instance_metric_data::_get_instance_metric_data_input::GetInstanceMetricDataInputBuilder;
pub use crate::operation::get_instance_metric_data::_get_instance_metric_data_output::GetInstanceMetricDataOutputBuilder;
impl crate::operation::get_instance_metric_data::builders::GetInstanceMetricDataInputBuilder {
/// Sends a request with this input using the given client.
pub async fn send_with(
self,
client: &crate::Client,
) -> ::std::result::Result<
crate::operation::get_instance_metric_data::GetInstanceMetricDataOutput,
::aws_smithy_runtime_api::client::result::SdkError<
crate::operation::get_instance_metric_data::GetInstanceMetricDataError,
::aws_smithy_runtime_api::client::orchestrator::HttpResponse,
>,
> {
let mut fluent_builder = client.get_instance_metric_data();
fluent_builder.inner = self;
fluent_builder.send().await
}
}
/// Fluent builder constructing a request to `GetInstanceMetricData`.
///
/// <p>Returns the data points for the specified Amazon Lightsail instance metric, given an instance name.</p>
/// <p>Metrics report the utilization of your resources, and the error counts generated by them. Monitor and collect metric data regularly to maintain the reliability, availability, and performance of your resources.</p>
#[derive(::std::clone::Clone, ::std::fmt::Debug)]
pub struct GetInstanceMetricDataFluentBuilder {
handle: ::std::sync::Arc<crate::client::Handle>,
inner: crate::operation::get_instance_metric_data::builders::GetInstanceMetricDataInputBuilder,
config_override: ::std::option::Option<crate::config::Builder>,
}
impl
crate::client::customize::internal::CustomizableSend<
crate::operation::get_instance_metric_data::GetInstanceMetricDataOutput,
crate::operation::get_instance_metric_data::GetInstanceMetricDataError,
> for GetInstanceMetricDataFluentBuilder
{
fn send(
self,
config_override: crate::config::Builder,
) -> crate::client::customize::internal::BoxFuture<
crate::client::customize::internal::SendResult<
crate::operation::get_instance_metric_data::GetInstanceMetricDataOutput,
crate::operation::get_instance_metric_data::GetInstanceMetricDataError,
>,
> {
::std::boxed::Box::pin(async move { self.config_override(config_override).send().await })
}
}
impl GetInstanceMetricDataFluentBuilder {
/// Creates a new `GetInstanceMetricDataFluentBuilder`.
pub(crate) fn new(handle: ::std::sync::Arc<crate::client::Handle>) -> Self {
Self {
handle,
inner: ::std::default::Default::default(),
config_override: ::std::option::Option::None,
}
}
/// Access the GetInstanceMetricData as a reference.
pub fn as_input(&self) -> &crate::operation::get_instance_metric_data::builders::GetInstanceMetricDataInputBuilder {
&self.inner
}
/// Sends the request and returns the response.
///
/// If an error occurs, an `SdkError` will be returned with additional details that
/// can be matched against.
///
/// By default, any retryable failures will be retried twice. Retry behavior
/// is configurable with the [RetryConfig](aws_smithy_types::retry::RetryConfig), which can be
/// set when configuring the client.
pub async fn send(
self,
) -> ::std::result::Result<
crate::operation::get_instance_metric_data::GetInstanceMetricDataOutput,
::aws_smithy_runtime_api::client::result::SdkError<
crate::operation::get_instance_metric_data::GetInstanceMetricDataError,
::aws_smithy_runtime_api::client::orchestrator::HttpResponse,
>,
> {
let input = self
.inner
.build()
.map_err(::aws_smithy_runtime_api::client::result::SdkError::construction_failure)?;
let runtime_plugins = crate::operation::get_instance_metric_data::GetInstanceMetricData::operation_runtime_plugins(
self.handle.runtime_plugins.clone(),
&self.handle.conf,
self.config_override,
);
crate::operation::get_instance_metric_data::GetInstanceMetricData::orchestrate(&runtime_plugins, input).await
}
/// Consumes this builder, creating a customizable operation that can be modified before being sent.
pub fn customize(
self,
) -> crate::client::customize::CustomizableOperation<
crate::operation::get_instance_metric_data::GetInstanceMetricDataOutput,
crate::operation::get_instance_metric_data::GetInstanceMetricDataError,
Self,
> {
crate::client::customize::CustomizableOperation::new(self)
}
pub(crate) fn config_override(mut self, config_override: impl ::std::convert::Into<crate::config::Builder>) -> Self {
self.set_config_override(::std::option::Option::Some(config_override.into()));
self
}
pub(crate) fn set_config_override(&mut self, config_override: ::std::option::Option<crate::config::Builder>) -> &mut Self {
self.config_override = config_override;
self
}
/// <p>The name of the instance for which you want to get metrics data.</p>
pub fn instance_name(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.inner = self.inner.instance_name(input.into());
self
}
/// <p>The name of the instance for which you want to get metrics data.</p>
pub fn set_instance_name(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.inner = self.inner.set_instance_name(input);
self
}
/// <p>The name of the instance for which you want to get metrics data.</p>
pub fn get_instance_name(&self) -> &::std::option::Option<::std::string::String> {
self.inner.get_instance_name()
}
/// <p>The metric for which you want to return information.</p>
/// <p>Valid instance metric names are listed below, along with the most useful <code>statistics</code> to include in your request, and the published <code>unit</code> value.</p>
/// <ul>
/// <li>
/// <p><b> <code>BurstCapacityPercentage</code> </b> - The percentage of CPU performance available for your instance to burst above its baseline. Your instance continuously accrues and consumes burst capacity. Burst capacity stops accruing when your instance's <code>BurstCapacityPercentage</code> reaches 100%. For more information, see <a href="https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-viewing-instance-burst-capacity">Viewing instance burst capacity in Amazon Lightsail</a>.</p>
/// <p><code>Statistics</code>: The most useful statistics are <code>Maximum</code> and <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Percent</code>.</p></li>
/// <li>
/// <p><b> <code>BurstCapacityTime</code> </b> - The available amount of time for your instance to burst at 100% CPU utilization. Your instance continuously accrues and consumes burst capacity. Burst capacity time stops accruing when your instance's <code>BurstCapacityPercentage</code> metric reaches 100%.</p>
/// <p>Burst capacity time is consumed at the full rate only when your instance operates at 100% CPU utilization. For example, if your instance operates at 50% CPU utilization in the burstable zone for a 5-minute period, then it consumes CPU burst capacity minutes at a 50% rate in that period. Your instance consumed 2 minutes and 30 seconds of CPU burst capacity minutes in the 5-minute period. For more information, see <a href="https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-viewing-instance-burst-capacity">Viewing instance burst capacity in Amazon Lightsail</a>.</p>
/// <p><code>Statistics</code>: The most useful statistics are <code>Maximum</code> and <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Seconds</code>.</p></li>
/// <li>
/// <p><b> <code>CPUUtilization</code> </b> - The percentage of allocated compute units that are currently in use on the instance. This metric identifies the processing power to run the applications on the instance. Tools in your operating system can show a lower percentage than Lightsail when the instance is not allocated a full processor core.</p>
/// <p><code>Statistics</code>: The most useful statistics are <code>Maximum</code> and <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Percent</code>.</p></li>
/// <li>
/// <p><b> <code>NetworkIn</code> </b> - The number of bytes received on all network interfaces by the instance. This metric identifies the volume of incoming network traffic to the instance. The number reported is the number of bytes received during the period. Because this metric is reported in 5-minute intervals, divide the reported number by 300 to find Bytes/second.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Bytes</code>.</p></li>
/// <li>
/// <p><b> <code>NetworkOut</code> </b> - The number of bytes sent out on all network interfaces by the instance. This metric identifies the volume of outgoing network traffic from the instance. The number reported is the number of bytes sent during the period. Because this metric is reported in 5-minute intervals, divide the reported number by 300 to find Bytes/second.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Bytes</code>.</p></li>
/// <li>
/// <p><b> <code>StatusCheckFailed</code> </b> - Reports whether the instance passed or failed both the instance status check and the system status check. This metric can be either 0 (passed) or 1 (failed). This metric data is available in 1-minute (60 seconds) granularity.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>StatusCheckFailed_Instance</code> </b> - Reports whether the instance passed or failed the instance status check. This metric can be either 0 (passed) or 1 (failed). This metric data is available in 1-minute (60 seconds) granularity.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>StatusCheckFailed_System</code> </b> - Reports whether the instance passed or failed the system status check. This metric can be either 0 (passed) or 1 (failed). This metric data is available in 1-minute (60 seconds) granularity.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>MetadataNoToken</code> </b> - Reports the number of times that the instance metadata service was successfully accessed without a token. This metric determines if there are any processes accessing instance metadata by using Instance Metadata Service Version 1, which doesn't use a token. If all requests use token-backed sessions, such as Instance Metadata Service Version 2, then the value is 0.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// </ul>
pub fn metric_name(mut self, input: crate::types::InstanceMetricName) -> Self {
self.inner = self.inner.metric_name(input);
self
}
/// <p>The metric for which you want to return information.</p>
/// <p>Valid instance metric names are listed below, along with the most useful <code>statistics</code> to include in your request, and the published <code>unit</code> value.</p>
/// <ul>
/// <li>
/// <p><b> <code>BurstCapacityPercentage</code> </b> - The percentage of CPU performance available for your instance to burst above its baseline. Your instance continuously accrues and consumes burst capacity. Burst capacity stops accruing when your instance's <code>BurstCapacityPercentage</code> reaches 100%. For more information, see <a href="https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-viewing-instance-burst-capacity">Viewing instance burst capacity in Amazon Lightsail</a>.</p>
/// <p><code>Statistics</code>: The most useful statistics are <code>Maximum</code> and <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Percent</code>.</p></li>
/// <li>
/// <p><b> <code>BurstCapacityTime</code> </b> - The available amount of time for your instance to burst at 100% CPU utilization. Your instance continuously accrues and consumes burst capacity. Burst capacity time stops accruing when your instance's <code>BurstCapacityPercentage</code> metric reaches 100%.</p>
/// <p>Burst capacity time is consumed at the full rate only when your instance operates at 100% CPU utilization. For example, if your instance operates at 50% CPU utilization in the burstable zone for a 5-minute period, then it consumes CPU burst capacity minutes at a 50% rate in that period. Your instance consumed 2 minutes and 30 seconds of CPU burst capacity minutes in the 5-minute period. For more information, see <a href="https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-viewing-instance-burst-capacity">Viewing instance burst capacity in Amazon Lightsail</a>.</p>
/// <p><code>Statistics</code>: The most useful statistics are <code>Maximum</code> and <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Seconds</code>.</p></li>
/// <li>
/// <p><b> <code>CPUUtilization</code> </b> - The percentage of allocated compute units that are currently in use on the instance. This metric identifies the processing power to run the applications on the instance. Tools in your operating system can show a lower percentage than Lightsail when the instance is not allocated a full processor core.</p>
/// <p><code>Statistics</code>: The most useful statistics are <code>Maximum</code> and <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Percent</code>.</p></li>
/// <li>
/// <p><b> <code>NetworkIn</code> </b> - The number of bytes received on all network interfaces by the instance. This metric identifies the volume of incoming network traffic to the instance. The number reported is the number of bytes received during the period. Because this metric is reported in 5-minute intervals, divide the reported number by 300 to find Bytes/second.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Bytes</code>.</p></li>
/// <li>
/// <p><b> <code>NetworkOut</code> </b> - The number of bytes sent out on all network interfaces by the instance. This metric identifies the volume of outgoing network traffic from the instance. The number reported is the number of bytes sent during the period. Because this metric is reported in 5-minute intervals, divide the reported number by 300 to find Bytes/second.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Bytes</code>.</p></li>
/// <li>
/// <p><b> <code>StatusCheckFailed</code> </b> - Reports whether the instance passed or failed both the instance status check and the system status check. This metric can be either 0 (passed) or 1 (failed). This metric data is available in 1-minute (60 seconds) granularity.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>StatusCheckFailed_Instance</code> </b> - Reports whether the instance passed or failed the instance status check. This metric can be either 0 (passed) or 1 (failed). This metric data is available in 1-minute (60 seconds) granularity.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>StatusCheckFailed_System</code> </b> - Reports whether the instance passed or failed the system status check. This metric can be either 0 (passed) or 1 (failed). This metric data is available in 1-minute (60 seconds) granularity.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>MetadataNoToken</code> </b> - Reports the number of times that the instance metadata service was successfully accessed without a token. This metric determines if there are any processes accessing instance metadata by using Instance Metadata Service Version 1, which doesn't use a token. If all requests use token-backed sessions, such as Instance Metadata Service Version 2, then the value is 0.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// </ul>
pub fn set_metric_name(mut self, input: ::std::option::Option<crate::types::InstanceMetricName>) -> Self {
self.inner = self.inner.set_metric_name(input);
self
}
/// <p>The metric for which you want to return information.</p>
/// <p>Valid instance metric names are listed below, along with the most useful <code>statistics</code> to include in your request, and the published <code>unit</code> value.</p>
/// <ul>
/// <li>
/// <p><b> <code>BurstCapacityPercentage</code> </b> - The percentage of CPU performance available for your instance to burst above its baseline. Your instance continuously accrues and consumes burst capacity. Burst capacity stops accruing when your instance's <code>BurstCapacityPercentage</code> reaches 100%. For more information, see <a href="https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-viewing-instance-burst-capacity">Viewing instance burst capacity in Amazon Lightsail</a>.</p>
/// <p><code>Statistics</code>: The most useful statistics are <code>Maximum</code> and <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Percent</code>.</p></li>
/// <li>
/// <p><b> <code>BurstCapacityTime</code> </b> - The available amount of time for your instance to burst at 100% CPU utilization. Your instance continuously accrues and consumes burst capacity. Burst capacity time stops accruing when your instance's <code>BurstCapacityPercentage</code> metric reaches 100%.</p>
/// <p>Burst capacity time is consumed at the full rate only when your instance operates at 100% CPU utilization. For example, if your instance operates at 50% CPU utilization in the burstable zone for a 5-minute period, then it consumes CPU burst capacity minutes at a 50% rate in that period. Your instance consumed 2 minutes and 30 seconds of CPU burst capacity minutes in the 5-minute period. For more information, see <a href="https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-viewing-instance-burst-capacity">Viewing instance burst capacity in Amazon Lightsail</a>.</p>
/// <p><code>Statistics</code>: The most useful statistics are <code>Maximum</code> and <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Seconds</code>.</p></li>
/// <li>
/// <p><b> <code>CPUUtilization</code> </b> - The percentage of allocated compute units that are currently in use on the instance. This metric identifies the processing power to run the applications on the instance. Tools in your operating system can show a lower percentage than Lightsail when the instance is not allocated a full processor core.</p>
/// <p><code>Statistics</code>: The most useful statistics are <code>Maximum</code> and <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Percent</code>.</p></li>
/// <li>
/// <p><b> <code>NetworkIn</code> </b> - The number of bytes received on all network interfaces by the instance. This metric identifies the volume of incoming network traffic to the instance. The number reported is the number of bytes received during the period. Because this metric is reported in 5-minute intervals, divide the reported number by 300 to find Bytes/second.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Bytes</code>.</p></li>
/// <li>
/// <p><b> <code>NetworkOut</code> </b> - The number of bytes sent out on all network interfaces by the instance. This metric identifies the volume of outgoing network traffic from the instance. The number reported is the number of bytes sent during the period. Because this metric is reported in 5-minute intervals, divide the reported number by 300 to find Bytes/second.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Bytes</code>.</p></li>
/// <li>
/// <p><b> <code>StatusCheckFailed</code> </b> - Reports whether the instance passed or failed both the instance status check and the system status check. This metric can be either 0 (passed) or 1 (failed). This metric data is available in 1-minute (60 seconds) granularity.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>StatusCheckFailed_Instance</code> </b> - Reports whether the instance passed or failed the instance status check. This metric can be either 0 (passed) or 1 (failed). This metric data is available in 1-minute (60 seconds) granularity.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>StatusCheckFailed_System</code> </b> - Reports whether the instance passed or failed the system status check. This metric can be either 0 (passed) or 1 (failed). This metric data is available in 1-minute (60 seconds) granularity.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>MetadataNoToken</code> </b> - Reports the number of times that the instance metadata service was successfully accessed without a token. This metric determines if there are any processes accessing instance metadata by using Instance Metadata Service Version 1, which doesn't use a token. If all requests use token-backed sessions, such as Instance Metadata Service Version 2, then the value is 0.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// </ul>
pub fn get_metric_name(&self) -> &::std::option::Option<crate::types::InstanceMetricName> {
self.inner.get_metric_name()
}
/// <p>The granularity, in seconds, of the returned data points.</p>
/// <p>The <code>StatusCheckFailed</code>, <code>StatusCheckFailed_Instance</code>, and <code>StatusCheckFailed_System</code> instance metric data is available in 1-minute (60 seconds) granularity. All other instance metric data is available in 5-minute (300 seconds) granularity.</p>
pub fn period(mut self, input: i32) -> Self {
self.inner = self.inner.period(input);
self
}
/// <p>The granularity, in seconds, of the returned data points.</p>
/// <p>The <code>StatusCheckFailed</code>, <code>StatusCheckFailed_Instance</code>, and <code>StatusCheckFailed_System</code> instance metric data is available in 1-minute (60 seconds) granularity. All other instance metric data is available in 5-minute (300 seconds) granularity.</p>
pub fn set_period(mut self, input: ::std::option::Option<i32>) -> Self {
self.inner = self.inner.set_period(input);
self
}
/// <p>The granularity, in seconds, of the returned data points.</p>
/// <p>The <code>StatusCheckFailed</code>, <code>StatusCheckFailed_Instance</code>, and <code>StatusCheckFailed_System</code> instance metric data is available in 1-minute (60 seconds) granularity. All other instance metric data is available in 5-minute (300 seconds) granularity.</p>
pub fn get_period(&self) -> &::std::option::Option<i32> {
self.inner.get_period()
}
/// <p>The start time of the time period.</p>
pub fn start_time(mut self, input: ::aws_smithy_types::DateTime) -> Self {
self.inner = self.inner.start_time(input);
self
}
/// <p>The start time of the time period.</p>
pub fn set_start_time(mut self, input: ::std::option::Option<::aws_smithy_types::DateTime>) -> Self {
self.inner = self.inner.set_start_time(input);
self
}
/// <p>The start time of the time period.</p>
pub fn get_start_time(&self) -> &::std::option::Option<::aws_smithy_types::DateTime> {
self.inner.get_start_time()
}
/// <p>The end time of the time period.</p>
pub fn end_time(mut self, input: ::aws_smithy_types::DateTime) -> Self {
self.inner = self.inner.end_time(input);
self
}
/// <p>The end time of the time period.</p>
pub fn set_end_time(mut self, input: ::std::option::Option<::aws_smithy_types::DateTime>) -> Self {
self.inner = self.inner.set_end_time(input);
self
}
/// <p>The end time of the time period.</p>
pub fn get_end_time(&self) -> &::std::option::Option<::aws_smithy_types::DateTime> {
self.inner.get_end_time()
}
/// <p>The unit for the metric data request. Valid units depend on the metric data being requested. For the valid units to specify with each available metric, see the <code>metricName</code> parameter.</p>
pub fn unit(mut self, input: crate::types::MetricUnit) -> Self {
self.inner = self.inner.unit(input);
self
}
/// <p>The unit for the metric data request. Valid units depend on the metric data being requested. For the valid units to specify with each available metric, see the <code>metricName</code> parameter.</p>
pub fn set_unit(mut self, input: ::std::option::Option<crate::types::MetricUnit>) -> Self {
self.inner = self.inner.set_unit(input);
self
}
/// <p>The unit for the metric data request. Valid units depend on the metric data being requested. For the valid units to specify with each available metric, see the <code>metricName</code> parameter.</p>
pub fn get_unit(&self) -> &::std::option::Option<crate::types::MetricUnit> {
self.inner.get_unit()
}
///
/// Appends an item to `statistics`.
///
/// To override the contents of this collection use [`set_statistics`](Self::set_statistics).
///
/// <p>The statistic for the metric.</p>
/// <p>The following statistics are available:</p>
/// <ul>
/// <li>
/// <p><code>Minimum</code> - The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.</p></li>
/// <li>
/// <p><code>Maximum</code> - The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.</p></li>
/// <li>
/// <p><code>Sum</code> - All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.</p></li>
/// <li>
/// <p><code>Average</code> - 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.</p></li>
/// <li>
/// <p><code>SampleCount</code> - The count, or number, of data points used for the statistical calculation.</p></li>
/// </ul>
pub fn statistics(mut self, input: crate::types::MetricStatistic) -> Self {
self.inner = self.inner.statistics(input);
self
}
/// <p>The statistic for the metric.</p>
/// <p>The following statistics are available:</p>
/// <ul>
/// <li>
/// <p><code>Minimum</code> - The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.</p></li>
/// <li>
/// <p><code>Maximum</code> - The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.</p></li>
/// <li>
/// <p><code>Sum</code> - All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.</p></li>
/// <li>
/// <p><code>Average</code> - 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.</p></li>
/// <li>
/// <p><code>SampleCount</code> - The count, or number, of data points used for the statistical calculation.</p></li>
/// </ul>
pub fn set_statistics(mut self, input: ::std::option::Option<::std::vec::Vec<crate::types::MetricStatistic>>) -> Self {
self.inner = self.inner.set_statistics(input);
self
}
/// <p>The statistic for the metric.</p>
/// <p>The following statistics are available:</p>
/// <ul>
/// <li>
/// <p><code>Minimum</code> - The lowest value observed during the specified period. Use this value to determine low volumes of activity for your application.</p></li>
/// <li>
/// <p><code>Maximum</code> - The highest value observed during the specified period. Use this value to determine high volumes of activity for your application.</p></li>
/// <li>
/// <p><code>Sum</code> - All values submitted for the matching metric added together. You can use this statistic to determine the total volume of a metric.</p></li>
/// <li>
/// <p><code>Average</code> - 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.</p></li>
/// <li>
/// <p><code>SampleCount</code> - The count, or number, of data points used for the statistical calculation.</p></li>
/// </ul>
pub fn get_statistics(&self) -> &::std::option::Option<::std::vec::Vec<crate::types::MetricStatistic>> {
self.inner.get_statistics()
}
}