You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* <p> The name of the custom metric. This will be used in the metric report submitted from the device/thing. Shouldn't begin with <code>aws:</code>.
3985
-
* Cannot be updated
3986
-
* once defined.</p>
3984
+
* <p> The name of the custom metric. This will be used in the metric report submitted from the
3985
+
* device/thing. The name can't begin with <code>aws:</code>. You can't change the name after you
3986
+
* define it.</p>
3987
3987
*/
3988
3988
metricName: string|undefined;
3989
3989
3990
3990
/**
3991
-
* <p>
3992
-
* Field
3993
-
* represents a friendly name in the console for the custom metric;
3994
-
* it
3995
-
* doesn't have to be unique. Don't use this name as the metric identifier in
3996
-
* the device metric report. Can be updated once defined.</p>
3991
+
* <p> The friendly name in the console for the custom metric. This name doesn't have to be
3992
+
* unique. Don't use this name as the metric identifier in the device metric report. You can
3993
+
* update the friendly name after you define it.</p>
3997
3994
*/
3998
3995
displayName?: string;
3999
3996
4000
3997
/**
4001
-
* <p>
4002
-
* The type of the custom metric. Types include <code>string-list</code>, <code>ip-address-list</code>, <code>number-list</code>, and <code>number</code>.
4003
-
* </p>
3998
+
* <p> The type of the custom metric. </p>
3999
+
* <important>
4000
+
* <p>The type <code>number</code> only takes a single metric value as an input, but when you
4001
+
* submit the metrics value in the DeviceMetrics report, you must pass it as an array with a
* The Amazon Resource Number (ARN) of the custom metric, e.g. <code>arn:<i>aws-partition</i>:iot:<i>region</i>:<i>accountId</i>:custommetric/<i>metricName</i>
4042
+
* <p> The Amazon Resource Number (ARN) of the custom metric. For example,
* <p>The hash algorithm used to code sign the file.</p>
5508
+
* <p>The hash algorithm used to code sign the file. You can use a string as the algorithm name if the target over-the-air (OTA) update devices are able to verify the signature that was generated using the same signature algorithm. For example, FreeRTOS uses <code>SHA256</code> or <code>SHA1</code>, so you can pass either of them based on which was used for generating the signature.</p>
5509
5509
*/
5510
5510
hashAlgorithm?: string;
5511
5511
5512
5512
/**
5513
-
* <p>The signature algorithm used to code sign the file.</p>
5513
+
* <p>The signature algorithm used to code sign the file. You can use a string as the algorithm name if the target over-the-air (OTA) update devices are able to verify the signature that was generated using the same signature algorithm. For example, FreeRTOS uses <code>ECDSA</code> or <code>RSA</code>, so you can pass either of them based on which was used for generating the signature.</p>
* The type of the custom metric. Types include <code>string-list</code>, <code>ip-address-list</code>, <code>number-list</code>, and <code>number</code>.
1203
-
* </p>
1201
+
* <p> The type of the custom metric. </p>
1202
+
* <important>
1203
+
* <p>The type <code>number</code> only takes a single metric value as an input, but while submitting the metrics value in the DeviceMetrics report, it must be passed as an array with a single value.</p>
* The type of the custom metric. Types include <code>string-list</code>, <code>ip-address-list</code>, <code>number-list</code>, and <code>number</code>.
2765
-
* </p>
2768
+
* <p> The type of the custom metric. </p>
2769
+
* <important>
2770
+
* <p>The type <code>number</code> only takes a single metric value as an input, but while submitting the metrics value in the DeviceMetrics report, it must be passed as an array with a single value.</p>
0 commit comments