From e4f6fb583df1eaca859392e5ddc9252c0a62396e Mon Sep 17 00:00:00 2001
From: awstools Deletes the specified anomaly detection model from your account.
+ * Deletes the specified anomaly detection model
+ * from your account.
+ * For more information
+ * about
+ * how to delete an anomaly detection model,
+ * see Deleting an anomaly detection model
+ * in the CloudWatch User Guide.
+ * Values
and Counts
method enables you to publish up to 150 values per metric
* with one PutMetricData
request, and
* supports retrieving percentile statistics on this data.
Each PutMetricData
request is limited to 40 KB in size for HTTP POST requests. You can
+ *
Each PutMetricData
request is limited to 1 MB in size for HTTP POST requests. You can
* send a payload compressed by gzip. Each request
- * is also limited to no more than 20 different metrics.
Although the Value
parameter accepts numbers of type
* Double
, CloudWatch rejects values that are either too small
* or too large. Values must be in the range of -2^360 to 2^360. In addition, special values (for example, NaN, +Infinity,
* -Infinity) are not supported.
You can use up to 10 dimensions per metric to further clarify what data the metric collects. Each dimension + *
You can use up to 30 dimensions per metric to further clarify what data the metric collects. Each dimension * consists of a Name and Value pair. For more information about specifying dimensions, see Publishing Metrics in the * Amazon CloudWatch User Guide.
* diff --git a/clients/client-cloudwatch/src/commands/DeleteAnomalyDetectorCommand.ts b/clients/client-cloudwatch/src/commands/DeleteAnomalyDetectorCommand.ts index 9388dd4c9857..9129538a4f93 100644 --- a/clients/client-cloudwatch/src/commands/DeleteAnomalyDetectorCommand.ts +++ b/clients/client-cloudwatch/src/commands/DeleteAnomalyDetectorCommand.ts @@ -28,7 +28,15 @@ export interface DeleteAnomalyDetectorCommandInput extends DeleteAnomalyDetector export interface DeleteAnomalyDetectorCommandOutput extends DeleteAnomalyDetectorOutput, __MetadataBearer {} /** - *Deletes the specified anomaly detection model from your account.
+ *+ * Deletes the specified anomaly detection model + * from your account. + * For more information + * about + * how to delete an anomaly detection model, + * see Deleting an anomaly detection model + * in the CloudWatch User Guide. + *
* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-cloudwatch/src/commands/PutMetricDataCommand.ts b/clients/client-cloudwatch/src/commands/PutMetricDataCommand.ts index 9f657d6c4a45..84469686599a 100644 --- a/clients/client-cloudwatch/src/commands/PutMetricDataCommand.ts +++ b/clients/client-cloudwatch/src/commands/PutMetricDataCommand.ts @@ -34,14 +34,14 @@ export interface PutMetricDataCommandOutput extends __MetadataBearer {} * theValues
and Counts
method enables you to publish up to 150 values per metric
* with one PutMetricData
request, and
* supports retrieving percentile statistics on this data.
- * Each PutMetricData
request is limited to 40 KB in size for HTTP POST requests. You can
+ *
Each PutMetricData
request is limited to 1 MB in size for HTTP POST requests. You can
* send a payload compressed by gzip. Each request
- * is also limited to no more than 20 different metrics.
Although the Value
parameter accepts numbers of type
* Double
, CloudWatch rejects values that are either too small
* or too large. Values must be in the range of -2^360 to 2^360. In addition, special values (for example, NaN, +Infinity,
* -Infinity) are not supported.
You can use up to 10 dimensions per metric to further clarify what data the metric collects. Each dimension + *
You can use up to 30 dimensions per metric to further clarify what data the metric collects. Each dimension * consists of a Name and Value pair. For more information about specifying dimensions, see Publishing Metrics in the * Amazon CloudWatch User Guide.
* diff --git a/clients/client-cloudwatch/src/models/models_0.ts b/clients/client-cloudwatch/src/models/models_0.ts index ef362a6e5b3f..c932057bca47 100644 --- a/clients/client-cloudwatch/src/models/models_0.ts +++ b/clients/client-cloudwatch/src/models/models_0.ts @@ -95,7 +95,7 @@ export interface AnomalyDetectorConfiguration { * your metrics, you are creating a new variation of that metric. For example, many Amazon EC2 metrics publish *InstanceId
as a dimension name, and the actual instance ID as the value for that dimension.
* You - * can assign up to 10 dimensions to a metric.
+ * can assign up to 30 dimensions to a metric. */ export interface Dimension { /** @@ -3095,7 +3095,7 @@ export interface PutMetricAlarmInput { * works as intended. *However, if the metric is published with multiple types of units and you don't specify a unit, the alarm's * behavior is not defined and - * it behaves predictably.
+ * it behaves unpredictably. *We recommend omitting Unit
so that you don't inadvertently
* specify an incorrect unit that is not published for this metric. Doing so
* causes the alarm to be stuck in the INSUFFICIENT DATA
state.
Array of numbers representing the values for the metric during the period. Each unique value is listed just once
* in this array, and the corresponding number in the Counts
array specifies the number of times that value occurred during the period.
- * You can include up to 150 unique values in each PutMetricData
action that specifies a Values
array.
PutMetricData
action that specifies a Values
array.
* Although the Values
array accepts numbers of type
* Double
, CloudWatch rejects values that are either too small
* or too large. Values must be in the range of -2^360 to 2^360. In addition, special values (for example, NaN, +Infinity,
@@ -3304,7 +3304,7 @@ export interface PutMetricDataInput {
Namespace: string | undefined;
/**
- *
The data for the metric. The array can include no more than 20 metrics per call.
+ *The data for the metric. The array can include no more than 1000 metrics per call.
*/ MetricData: MetricDatum[] | undefined; } diff --git a/codegen/sdk-codegen/aws-models/cloudwatch.json b/codegen/sdk-codegen/aws-models/cloudwatch.json index 4c5aac6c270c..eef5e98612be 100644 --- a/codegen/sdk-codegen/aws-models/cloudwatch.json +++ b/codegen/sdk-codegen/aws-models/cloudwatch.json @@ -851,7 +851,7 @@ } ], "traits": { - "smithy.api#documentation": "Deletes the specified anomaly detection model from your account.
" + "smithy.api#documentation": "\n\t\t\tDeletes the specified anomaly detection model \n\t\t\tfrom your account.\n\t\t\tFor more information \n\t\t\tabout \n\t\t\thow to delete an anomaly detection model, \n\t\t\tsee Deleting an anomaly detection model \n\t\t\tin the CloudWatch User Guide. \n\t\t
" } }, "com.amazonaws.cloudwatch#DeleteAnomalyDetectorInput": { @@ -1492,7 +1492,7 @@ } }, "traits": { - "smithy.api#documentation": "A dimension is a name/value pair that is part of the identity of a metric. Because dimensions are part of the unique \n\t\t\tidentifier for a metric, whenever you add a unique name/value pair to one of \n\t\t\tyour metrics, you are creating a new variation of that metric. For example, many Amazon EC2 metrics publish\n\t\tInstanceId
as a dimension name, and the actual instance ID as the value for that dimension.
You \n\t\tcan assign up to 10 dimensions to a metric.
" + "smithy.api#documentation": "A dimension is a name/value pair that is part of the identity of a metric. Because dimensions are part of the unique \n\t\t\tidentifier for a metric, whenever you add a unique name/value pair to one of \n\t\t\tyour metrics, you are creating a new variation of that metric. For example, many Amazon EC2 metrics publish\n\t\tInstanceId
as a dimension name, and the actual instance ID as the value for that dimension.
You \n\t\tcan assign up to 30 dimensions to a metric.
" } }, "com.amazonaws.cloudwatch#DimensionFilter": { @@ -1542,7 +1542,7 @@ "traits": { "smithy.api#length": { "min": 1, - "max": 255 + "max": 1024 } } }, @@ -1554,7 +1554,7 @@ "traits": { "smithy.api#length": { "min": 0, - "max": 10 + "max": 30 } } }, @@ -1726,10 +1726,7 @@ "type": "string" }, "com.amazonaws.cloudwatch#ExtendedStatistic": { - "type": "string", - "traits": { - "smithy.api#pattern": "^p(\\d{1,2}(\\.\\d{0,2})?|100)$" - } + "type": "string" }, "com.amazonaws.cloudwatch#ExtendedStatistics": { "type": "list", @@ -3560,7 +3557,7 @@ "Values": { "target": "com.amazonaws.cloudwatch#Values", "traits": { - "smithy.api#documentation": "Array of numbers representing the values for the metric during the period. Each unique value is listed just once\n\t\tin this array, and the corresponding number in the Counts
array specifies the number of times that value occurred during the period.\n\t\tYou can include up to 150 unique values in each PutMetricData
action that specifies a Values
array.
Although the Values
array accepts numbers of type\n\t\t\tDouble
, CloudWatch rejects values that are either too small\n\t\t\tor too large. Values must be in the range of -2^360 to 2^360. In addition, special values (for example, NaN, +Infinity,\n\t\t\t-Infinity) are not supported.
Array of numbers representing the values for the metric during the period. Each unique value is listed just once\n\t\tin this array, and the corresponding number in the Counts
array specifies the number of times that value occurred during the period.\n\t\tYou can include up to 500 unique values in each PutMetricData
action that specifies a Values
array.
Although the Values
array accepts numbers of type\n\t\t\tDouble
, CloudWatch rejects values that are either too small\n\t\t\tor too large. Values must be in the range of -2^360 to 2^360. In addition, special values (for example, NaN, +Infinity,\n\t\t\t-Infinity) are not supported.
The unit of measure for the statistic. For example, the units for the Amazon EC2\n\t\t\tNetworkIn metric are Bytes because NetworkIn tracks the number of bytes that an instance\n\t\t\treceives on all network interfaces. You can also specify a unit when you create a custom\n\t\t\tmetric. Units help provide conceptual meaning to your data. Metric data points that\n\t\t\tspecify a unit of measure, such as Percent, are aggregated separately.
\n\t\tIf you don't specify Unit
, CloudWatch retrieves all unit types that have been published for the\n\t\t\tmetric and attempts to evaluate the alarm.\n\t\t\tUsually, metrics are\n\t\t\tpublished with only one unit, so the alarm\n\t\t\tworks as intended.
However, if the metric is published with multiple types of units and you don't specify a unit, the alarm's\n\t\t\tbehavior is not defined and\n\t\t\tit behaves predictably.
\n\t\tWe recommend omitting Unit
so that you don't inadvertently\n\t\t\tspecify an incorrect unit that is not published for this metric. Doing so \n\t\t\tcauses the alarm to be stuck in the INSUFFICIENT DATA
state.
The unit of measure for the statistic. For example, the units for the Amazon EC2\n\t\t\tNetworkIn metric are Bytes because NetworkIn tracks the number of bytes that an instance\n\t\t\treceives on all network interfaces. You can also specify a unit when you create a custom\n\t\t\tmetric. Units help provide conceptual meaning to your data. Metric data points that\n\t\t\tspecify a unit of measure, such as Percent, are aggregated separately.
\n\t\tIf you don't specify Unit
, CloudWatch retrieves all unit types that have been published for the\n\t\t\tmetric and attempts to evaluate the alarm.\n\t\t\tUsually, metrics are\n\t\t\tpublished with only one unit, so the alarm\n\t\t\tworks as intended.
However, if the metric is published with multiple types of units and you don't specify a unit, the alarm's\n\t\t\tbehavior is not defined and\n\t\t\tit behaves unpredictably.
\n\t\tWe recommend omitting Unit
so that you don't inadvertently\n\t\t\tspecify an incorrect unit that is not published for this metric. Doing so \n\t\t\tcauses the alarm to be stuck in the INSUFFICIENT DATA
state.
Publishes metric data points to Amazon CloudWatch. CloudWatch associates\n\t\t\tthe data points with the specified metric. If the specified metric does not exist,\n\t\t\tCloudWatch creates the metric. When CloudWatch creates a metric, it can\n\t\t\ttake up to fifteen minutes for the metric to appear in calls to ListMetrics.
\n\n\t\tYou can publish either individual data points in the Value
field, or \n\t\tarrays of values and the number of times each value occurred during the period by using the \n\t\tValues
and Counts
fields in the MetricDatum
structure. Using\n\t\tthe Values
and Counts
method enables you to publish up to 150 values per metric\n\t\t\twith one PutMetricData
request, and\n\t\tsupports retrieving percentile statistics on this data.
Each PutMetricData
request is limited to 40 KB in size for HTTP POST requests. You can \n\t\t\tsend a payload compressed by gzip. Each request\n\t\tis also limited to no more than 20 different metrics.
Although the Value
parameter accepts numbers of type\n\t\t\tDouble
, CloudWatch rejects values that are either too small\n\t\t\tor too large. Values must be in the range of -2^360 to 2^360. In addition, special values (for example, NaN, +Infinity,\n\t\t\t-Infinity) are not supported.
You can use up to 10 dimensions per metric to further clarify what data the metric collects. Each dimension\n\t\t\tconsists of a Name and Value pair. For more information about specifying dimensions, see Publishing Metrics in the\n\t\t\tAmazon CloudWatch User Guide.
\n\n\t\tYou specify the time stamp to be associated with each data point. You can specify\n\t\ttime stamps that are as much as two weeks before the current date, and as much as 2 hours after \n\t\tthe current day and time.
\n\t\tData points with time stamps from 24 hours ago or longer can take at least 48\n\t\t\thours to become available for GetMetricData or \n\t\t\tGetMetricStatistics from the time they \n\t\t\tare submitted. Data points with time stamps between 3 and 24 hours ago can take as much as 2 hours to become available\n\t\t\tfor for GetMetricData or \n\t\t\tGetMetricStatistics.
\n\t\tCloudWatch needs raw data points to calculate percentile statistics. If you publish \n\t\t\tdata using a statistic set instead, you can only retrieve \n\t\t\tpercentile statistics for this data if one of the following conditions is true:
\n\t\t\tThe SampleCount
value of the statistic set is 1 and Min
,\n\t\t\t\t\tMax
, and Sum
are all equal.
The Min
and\n\t\t\t\t\tMax
are equal, and Sum
is equal to Min
\n\t\t\t\t\tmultiplied by SampleCount
.
Publishes metric data points to Amazon CloudWatch. CloudWatch associates\n\t\t\tthe data points with the specified metric. If the specified metric does not exist,\n\t\t\tCloudWatch creates the metric. When CloudWatch creates a metric, it can\n\t\t\ttake up to fifteen minutes for the metric to appear in calls to ListMetrics.
\n\n\t\tYou can publish either individual data points in the Value
field, or \n\t\tarrays of values and the number of times each value occurred during the period by using the \n\t\tValues
and Counts
fields in the MetricDatum
structure. Using\n\t\tthe Values
and Counts
method enables you to publish up to 150 values per metric\n\t\t\twith one PutMetricData
request, and\n\t\tsupports retrieving percentile statistics on this data.
Each PutMetricData
request is limited to 1 MB in size for HTTP POST requests. You can \n\t\t\tsend a payload compressed by gzip. Each request\n\t\tis also limited to no more than 1000 different metrics.
Although the Value
parameter accepts numbers of type\n\t\t\tDouble
, CloudWatch rejects values that are either too small\n\t\t\tor too large. Values must be in the range of -2^360 to 2^360. In addition, special values (for example, NaN, +Infinity,\n\t\t\t-Infinity) are not supported.
You can use up to 30 dimensions per metric to further clarify what data the metric collects. Each dimension\n\t\t\tconsists of a Name and Value pair. For more information about specifying dimensions, see Publishing Metrics in the\n\t\t\tAmazon CloudWatch User Guide.
\n\n\t\tYou specify the time stamp to be associated with each data point. You can specify\n\t\ttime stamps that are as much as two weeks before the current date, and as much as 2 hours after \n\t\tthe current day and time.
\n\t\tData points with time stamps from 24 hours ago or longer can take at least 48\n\t\t\thours to become available for GetMetricData or \n\t\t\tGetMetricStatistics from the time they \n\t\t\tare submitted. Data points with time stamps between 3 and 24 hours ago can take as much as 2 hours to become available\n\t\t\tfor for GetMetricData or \n\t\t\tGetMetricStatistics.
\n\t\tCloudWatch needs raw data points to calculate percentile statistics. If you publish \n\t\t\tdata using a statistic set instead, you can only retrieve \n\t\t\tpercentile statistics for this data if one of the following conditions is true:
\n\t\t\tThe SampleCount
value of the statistic set is 1 and Min
,\n\t\t\t\t\tMax
, and Sum
are all equal.
The Min
and\n\t\t\t\t\tMax
are equal, and Sum
is equal to Min
\n\t\t\t\t\tmultiplied by SampleCount
.
The data for the metric. The array can include no more than 20 metrics per call.
", + "smithy.api#documentation": "The data for the metric. The array can include no more than 1000 metrics per call.
", "smithy.api#required": {} } }