1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
pub use crate::operation::get_load_balancer_metric_data::_get_load_balancer_metric_data_input::GetLoadBalancerMetricDataInputBuilder;
pub use crate::operation::get_load_balancer_metric_data::_get_load_balancer_metric_data_output::GetLoadBalancerMetricDataOutputBuilder;
impl crate::operation::get_load_balancer_metric_data::builders::GetLoadBalancerMetricDataInputBuilder {
/// 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_load_balancer_metric_data::GetLoadBalancerMetricDataOutput,
::aws_smithy_runtime_api::client::result::SdkError<
crate::operation::get_load_balancer_metric_data::GetLoadBalancerMetricDataError,
::aws_smithy_runtime_api::client::orchestrator::HttpResponse,
>,
> {
let mut fluent_builder = client.get_load_balancer_metric_data();
fluent_builder.inner = self;
fluent_builder.send().await
}
}
/// Fluent builder constructing a request to `GetLoadBalancerMetricData`.
///
/// <p>Returns information about health metrics for your Lightsail load balancer.</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 GetLoadBalancerMetricDataFluentBuilder {
handle: ::std::sync::Arc<crate::client::Handle>,
inner: crate::operation::get_load_balancer_metric_data::builders::GetLoadBalancerMetricDataInputBuilder,
config_override: ::std::option::Option<crate::config::Builder>,
}
impl
crate::client::customize::internal::CustomizableSend<
crate::operation::get_load_balancer_metric_data::GetLoadBalancerMetricDataOutput,
crate::operation::get_load_balancer_metric_data::GetLoadBalancerMetricDataError,
> for GetLoadBalancerMetricDataFluentBuilder
{
fn send(
self,
config_override: crate::config::Builder,
) -> crate::client::customize::internal::BoxFuture<
crate::client::customize::internal::SendResult<
crate::operation::get_load_balancer_metric_data::GetLoadBalancerMetricDataOutput,
crate::operation::get_load_balancer_metric_data::GetLoadBalancerMetricDataError,
>,
> {
::std::boxed::Box::pin(async move { self.config_override(config_override).send().await })
}
}
impl GetLoadBalancerMetricDataFluentBuilder {
/// Creates a new `GetLoadBalancerMetricDataFluentBuilder`.
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 GetLoadBalancerMetricData as a reference.
pub fn as_input(&self) -> &crate::operation::get_load_balancer_metric_data::builders::GetLoadBalancerMetricDataInputBuilder {
&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_load_balancer_metric_data::GetLoadBalancerMetricDataOutput,
::aws_smithy_runtime_api::client::result::SdkError<
crate::operation::get_load_balancer_metric_data::GetLoadBalancerMetricDataError,
::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_load_balancer_metric_data::GetLoadBalancerMetricData::operation_runtime_plugins(
self.handle.runtime_plugins.clone(),
&self.handle.conf,
self.config_override,
);
crate::operation::get_load_balancer_metric_data::GetLoadBalancerMetricData::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_load_balancer_metric_data::GetLoadBalancerMetricDataOutput,
crate::operation::get_load_balancer_metric_data::GetLoadBalancerMetricDataError,
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 load balancer.</p>
pub fn load_balancer_name(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
self.inner = self.inner.load_balancer_name(input.into());
self
}
/// <p>The name of the load balancer.</p>
pub fn set_load_balancer_name(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
self.inner = self.inner.set_load_balancer_name(input);
self
}
/// <p>The name of the load balancer.</p>
pub fn get_load_balancer_name(&self) -> &::std::option::Option<::std::string::String> {
self.inner.get_load_balancer_name()
}
/// <p>The metric for which you want to return information.</p>
/// <p>Valid load balancer 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>ClientTLSNegotiationErrorCount</code> </b> - 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.</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>HealthyHostCount</code> </b> - The number of target instances that are considered healthy.</p>
/// <p><code>Statistics</code>: The most useful statistic are <code>Average</code>, <code>Minimum</code>, and <code>Maximum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_2XX_Count</code> </b> - The number of HTTP 2XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_3XX_Count</code> </b> - The number of HTTP 3XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_4XX_Count</code> </b> - The number of HTTP 4XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_5XX_Count</code> </b> - The number of HTTP 5XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_LB_4XX_Count</code> </b> - 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.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_LB_5XX_Count</code> </b> - 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.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>InstanceResponseTime</code> </b> - The time elapsed, in seconds, after the request leaves the load balancer until a response from the target instance is received.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Seconds</code>.</p></li>
/// <li>
/// <p><b> <code>RejectedConnectionCount</code> </b> - The number of connections that were rejected because the load balancer had reached its maximum number of connections.</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>RequestCount</code> </b> - 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.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>UnhealthyHostCount</code> </b> - The number of target instances that are considered unhealthy.</p>
/// <p><code>Statistics</code>: The most useful statistic are <code>Average</code>, <code>Minimum</code>, and <code>Maximum</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::LoadBalancerMetricName) -> Self {
self.inner = self.inner.metric_name(input);
self
}
/// <p>The metric for which you want to return information.</p>
/// <p>Valid load balancer 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>ClientTLSNegotiationErrorCount</code> </b> - 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.</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>HealthyHostCount</code> </b> - The number of target instances that are considered healthy.</p>
/// <p><code>Statistics</code>: The most useful statistic are <code>Average</code>, <code>Minimum</code>, and <code>Maximum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_2XX_Count</code> </b> - The number of HTTP 2XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_3XX_Count</code> </b> - The number of HTTP 3XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_4XX_Count</code> </b> - The number of HTTP 4XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_5XX_Count</code> </b> - The number of HTTP 5XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_LB_4XX_Count</code> </b> - 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.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_LB_5XX_Count</code> </b> - 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.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>InstanceResponseTime</code> </b> - The time elapsed, in seconds, after the request leaves the load balancer until a response from the target instance is received.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Seconds</code>.</p></li>
/// <li>
/// <p><b> <code>RejectedConnectionCount</code> </b> - The number of connections that were rejected because the load balancer had reached its maximum number of connections.</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>RequestCount</code> </b> - 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.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>UnhealthyHostCount</code> </b> - The number of target instances that are considered unhealthy.</p>
/// <p><code>Statistics</code>: The most useful statistic are <code>Average</code>, <code>Minimum</code>, and <code>Maximum</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::LoadBalancerMetricName>) -> Self {
self.inner = self.inner.set_metric_name(input);
self
}
/// <p>The metric for which you want to return information.</p>
/// <p>Valid load balancer 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>ClientTLSNegotiationErrorCount</code> </b> - 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.</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>HealthyHostCount</code> </b> - The number of target instances that are considered healthy.</p>
/// <p><code>Statistics</code>: The most useful statistic are <code>Average</code>, <code>Minimum</code>, and <code>Maximum</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_2XX_Count</code> </b> - The number of HTTP 2XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_3XX_Count</code> </b> - The number of HTTP 3XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_4XX_Count</code> </b> - The number of HTTP 4XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_Instance_5XX_Count</code> </b> - The number of HTTP 5XX response codes generated by the target instances. This does not include any response codes generated by the load balancer.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_LB_4XX_Count</code> </b> - 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.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>HTTPCode_LB_5XX_Count</code> </b> - 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.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>InstanceResponseTime</code> </b> - The time elapsed, in seconds, after the request leaves the load balancer until a response from the target instance is received.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Average</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Seconds</code>.</p></li>
/// <li>
/// <p><b> <code>RejectedConnectionCount</code> </b> - The number of connections that were rejected because the load balancer had reached its maximum number of connections.</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>RequestCount</code> </b> - 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.</p>
/// <p><code>Statistics</code>: The most useful statistic is <code>Sum</code>. Note that <code>Minimum</code>, <code>Maximum</code>, and <code>Average</code> all return <code>1</code>.</p>
/// <p><code>Unit</code>: The published unit is <code>Count</code>.</p></li>
/// <li>
/// <p><b> <code>UnhealthyHostCount</code> </b> - The number of target instances that are considered unhealthy.</p>
/// <p><code>Statistics</code>: The most useful statistic are <code>Average</code>, <code>Minimum</code>, and <code>Maximum</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::LoadBalancerMetricName> {
self.inner.get_metric_name()
}
/// <p>The granularity, in seconds, of the returned data points.</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>
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>
pub fn get_period(&self) -> &::std::option::Option<i32> {
self.inner.get_period()
}
/// <p>The start time of the 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 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 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 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 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 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 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 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 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()
}
}