#[non_exhaustive]pub struct PutMetricDataInput {
pub namespace: Option<String>,
pub metric_data: Option<Vec<MetricDatum>>,
pub entity_metric_data: Option<Vec<EntityMetricData>>,
pub strict_entity_validation: Option<bool>,
}
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.namespace: Option<String>
The namespace for the metric data. You can use ASCII characters for the namespace, except for control characters which are not supported.
To avoid conflicts with Amazon Web Services service namespaces, you should not specify a namespace that begins with AWS/
metric_data: Option<Vec<MetricDatum>>
The data for the metrics. Use this parameter if your metrics do not contain associated entities. The array can include no more than 1000 metrics per call.
The limit of metrics allowed, 1000, is the sum of both EntityMetricData
and MetricData
metrics.
entity_metric_data: Option<Vec<EntityMetricData>>
Data for metrics that contain associated entity information. You can include up to two EntityMetricData
objects, each of which can contain a single Entity
and associated metrics.
The limit of metrics allowed, 1000, is the sum of both EntityMetricData
and MetricData
metrics.
strict_entity_validation: Option<bool>
Whether to accept valid metric data when an invalid entity is sent.
-
When set to
true
: Any validation error (for entity or metric data) will fail the entire request, and no data will be ingested. The failed operation will return a 400 result with the error. -
When set to
false
: Validation errors in the entity will not associate the metric with the entity, but the metric data will still be accepted and ingested. Validation errors in the metric data will fail the entire request, and no data will be ingested.In the case of an invalid entity, the operation will return a
200
status, but an additional response header will contain information about the validation errors. The new header,X-Amzn-Failure-Message
is an enumeration of the following values:-
InvalidEntity
- The provided entity is invalid. -
InvalidKeyAttributes
- The providedKeyAttributes
of an entity is invalid. -
InvalidAttributes
- The providedAttributes
of an entity is invalid. -
InvalidTypeValue
- The providedType
in theKeyAttributes
of an entity is invalid. -
EntitySizeTooLarge
- The number ofEntityMetricData
objects allowed is 2. -
MissingRequiredFields
- There are missing required fields in theKeyAttributes
for the providedType
.
For details of the requirements for specifying an entity, see How to add related information to telemetry in the CloudWatch User Guide.
-
This parameter is required when EntityMetricData
is included.
Implementations§
Source§impl PutMetricDataInput
impl PutMetricDataInput
Sourcepub fn namespace(&self) -> Option<&str>
pub fn namespace(&self) -> Option<&str>
The namespace for the metric data. You can use ASCII characters for the namespace, except for control characters which are not supported.
To avoid conflicts with Amazon Web Services service namespaces, you should not specify a namespace that begins with AWS/
Sourcepub fn metric_data(&self) -> &[MetricDatum]
pub fn metric_data(&self) -> &[MetricDatum]
The data for the metrics. Use this parameter if your metrics do not contain associated entities. The array can include no more than 1000 metrics per call.
The limit of metrics allowed, 1000, is the sum of both EntityMetricData
and MetricData
metrics.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .metric_data.is_none()
.
Sourcepub fn entity_metric_data(&self) -> &[EntityMetricData]
pub fn entity_metric_data(&self) -> &[EntityMetricData]
Data for metrics that contain associated entity information. You can include up to two EntityMetricData
objects, each of which can contain a single Entity
and associated metrics.
The limit of metrics allowed, 1000, is the sum of both EntityMetricData
and MetricData
metrics.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .entity_metric_data.is_none()
.
Sourcepub fn strict_entity_validation(&self) -> Option<bool>
pub fn strict_entity_validation(&self) -> Option<bool>
Whether to accept valid metric data when an invalid entity is sent.
-
When set to
true
: Any validation error (for entity or metric data) will fail the entire request, and no data will be ingested. The failed operation will return a 400 result with the error. -
When set to
false
: Validation errors in the entity will not associate the metric with the entity, but the metric data will still be accepted and ingested. Validation errors in the metric data will fail the entire request, and no data will be ingested.In the case of an invalid entity, the operation will return a
200
status, but an additional response header will contain information about the validation errors. The new header,X-Amzn-Failure-Message
is an enumeration of the following values:-
InvalidEntity
- The provided entity is invalid. -
InvalidKeyAttributes
- The providedKeyAttributes
of an entity is invalid. -
InvalidAttributes
- The providedAttributes
of an entity is invalid. -
InvalidTypeValue
- The providedType
in theKeyAttributes
of an entity is invalid. -
EntitySizeTooLarge
- The number ofEntityMetricData
objects allowed is 2. -
MissingRequiredFields
- There are missing required fields in theKeyAttributes
for the providedType
.
For details of the requirements for specifying an entity, see How to add related information to telemetry in the CloudWatch User Guide.
-
This parameter is required when EntityMetricData
is included.
Source§impl PutMetricDataInput
impl PutMetricDataInput
Sourcepub fn builder() -> PutMetricDataInputBuilder
pub fn builder() -> PutMetricDataInputBuilder
Creates a new builder-style object to manufacture PutMetricDataInput
.
Trait Implementations§
Source§impl Clone for PutMetricDataInput
impl Clone for PutMetricDataInput
Source§fn clone(&self) -> PutMetricDataInput
fn clone(&self) -> PutMetricDataInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for PutMetricDataInput
impl Debug for PutMetricDataInput
Source§impl PartialEq for PutMetricDataInput
impl PartialEq for PutMetricDataInput
impl StructuralPartialEq for PutMetricDataInput
Auto Trait Implementations§
impl Freeze for PutMetricDataInput
impl RefUnwindSafe for PutMetricDataInput
impl Send for PutMetricDataInput
impl Sync for PutMetricDataInput
impl Unpin for PutMetricDataInput
impl UnwindSafe for PutMetricDataInput
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);