class Aws::IoT::Types::CreateCustomMetricRequest

@return [String]
not need to pass this option.
**A suitable default value is auto-generated.** You should normally
SDKs will automatically generate a unique client request.
different token, an exception occurs. If you omit this value, AWS
try to create a new custom metric that already exists with a
Each custom metric must have a unique client request token. If you
@!attribute [rw] client_request_token
@return [Array<Types::Tag>]
Metadata that can be used to manage the custom metric.
@!attribute [rw] tags
@return [String]
‘ip-address-list`, `number-list`, and `number`.
The type of the custom metric. Types include `string-list`,
@!attribute [rw] metric_type
@return [String]
defined.
metric identifier in the device metric report. Can be updated once
metric; it doesn’t have to be unique. Don’t use this name as the
Field represents a friendly name in the console for the custom
@!attribute [rw] display_name
@return [String]
‘aws:`. Cannot be updated once defined.
report submitted from the device/thing. Shouldn’t begin with
The name of the custom metric. This will be used in the metric
@!attribute [rw] metric_name
}
client_request_token: “ClientRequestToken”, # required
],
},
value: “TagValue”,
key: “TagKey”, # required
{
tags: [
metric_type: “string-list”, # required, accepts string-list, ip-address-list, number-list, number
display_name: “CustomMetricDisplayName”,
metric_name: “MetricName”, # required
{
data as a hash:
@note When making an API call, you may pass CreateCustomMetricRequest