Amazon IoT metrics and dimensions
When you interact with Amazon IoT, the service sends the following metrics and dimensions to CloudWatch every minute. You can use the following procedures to view the metrics for Amazon IoT.
To view metrics (CloudWatch console)
Metrics are grouped first by the service namespace, and then by the various dimension combinations within each namespace.
-
Open the CloudWatch console
. -
In the navigation pane, choose Metrics and then choose All metrics.
-
In the Browse tab, search for Amazon IoT to view the list of metrics.
To view metrics (CLI)
-
At a command prompt, use the following command:
aws cloudwatch list-metrics --namespace "Amazon/IoT"
CloudWatch displays the following groups of metrics for Amazon IoT:
- Amazon IoT metrics
- Amazon IoT Core credential provider metrics
- Rule metrics
- Rule action metrics
- HTTP action specific metrics
- Message broker metrics
- Device shadow metrics
- Jobs metrics
- Device Defender audit metrics
- Device Defender detect metrics
- Device provisioning metrics
- Fleet indexing metrics
- Dimensions for metrics
Amazon IoT metrics
Metric | Description |
---|---|
|
The number of failure events associated with adding a thing to a dynamic
thing group. The |
|
The singular batch of log events that has failed to publish due to throttling errors. |
|
The number of log events within the batch that have failed to publish due to throttling errors. |
Amazon IoT Core credential provider metrics
Metric | Description |
---|---|
|
The number of successful |
Rule metrics
Metric | Description |
---|---|
|
The number of JSON parse errors that occurred in messages published on a
topic on which a rule is listening. The |
|
The number of messages throttled by the rules engine because of malicious
behavior or because the number of messages exceeds the rules engine's throttle
limit. The |
|
The rule to be triggered could not be found. The |
|
The number of Amazon IoT rules executed. |
|
The number of incoming messages published on a topic on which a rule is
listening. The |
Rule action metrics
Metric | Description |
---|---|
|
The number of failed rule action invocations. The |
|
The number of successful rule action invocations. The |
ErrorActionFailure |
The number of failed error actions. The RuleName dimension
contains the name of the rule that specifies the action. The
ActionType dimension contains the type of action that was
invoked. |
ErrorActionSuccess |
The number of successful error actions. The RuleName dimension
contains the name of the rule that specifies the action. The
ActionType dimension contains the type of action that was
invoked. |
HTTP action specific metrics
Metric | Description |
---|---|
|
Generated if the status code of the response from the downstream web service/application is not 2xx, 4xx or 5xx. |
|
Generated if the status code of the response from the downstream web service/application is between 400 and 499. |
|
Generated if the status code of the response from the downstream web service/application is between 500 and 599. |
|
Generated if an endpoint URL, after substitution templates are replaced,
does not start with |
|
Generated if the downstream web service/application does not return response within request timeout limit. For more information, see Service Quotas. |
|
Generated if the URL is valid, but the service does not exist or is unreachable. |
Message broker metrics
Note
The message broker metrics are displayed in the CloudWatch console under Protocol Metrics.
Metric | Description |
---|---|
|
The number of connection requests that could not be authorized by the
message broker. The |
|
The number of connection requests rejected because the MQTT message did not
meet the requirements defined in Amazon IoT quotas. The |
|
The number of connection requests throttled because the client exceeded the
allowed connect request rate for a specific client ID. The |
|
The number of connection requests that failed because an internal error
occurred. The |
|
The number of successful connections to the message broker. The
|
|
The number of connection requests that were throttled because the account
exceeded the allowed connect request rate. The |
|
The number of ping messages received by the message broker. The
|
|
The number of publish requests the message broker was unable to authorize.
The |
|
The number of publish requests rejected by the message broker because the
message did not meet the requirements defined in Amazon IoT quotas. The |
|
The number of publish requests the message broker failed to process because
an internal error occurred. The |
|
The number of publish requests successfully processed by the message broker.
The |
|
The number of publish request that were throttled because the client
exceeded the allowed inbound message rate. The |
|
The number of publish requests made by the message broker that could not be
authorized by Amazon IoT. The |
|
The number of publish requests made by the message broker that were rejected
because the message did not meet the requirements defined in Amazon IoT quotas. The |
|
The number of publish requests successfully made by the message broker. The
|
PublishOut.Throttle |
The number of publish requests that were throttled because the client
exceeded the allowed outbound message rate. The |
|
The number of publish requests with the |
PublishRetained.ServerError |
The number of retained publish requests the message broker failed to process
because an internal error occurred. The |
|
The number of publish requests with the |
|
The number of publish requests with the |
|
The number of stored messages that were successfully processed by the message broker for clients that were disconnected from their persistent session. Messages with a QoS of 1 are stored while a client with a persistent session is disconnected. |
|
The number of messages that couldn't be stored and were throttled while clients with persistent sessions were disconnected. This occurs when clients exceed the Queued messages per second per account limit. Messages with a QoS of 1 are stored while a client with a persistent session is disconnected. |
|
The number of messages that haven't been stored for a persistent session because of an internal error. When clients with a persistent session are disconnected, messages with a Quality of Service (QoS) of 1 are stored. |
|
The number of subscription requests made by a client that could not be
authorized. The |
|
The number of subscribe requests that were rejected because the
|
|
The number of subscribe requests that were rejected because an internal
error occurred. The |
|
The number of subscribe requests that were successfully processed by the
message broker. The |
|
The number of subscribe requests that were throttled because the client
exceeded the allowed subscribe request rate. The |
Throttle.Exceeded |
This metric will display in CloudWatch when an MQTT client is throttled on packets per second per connection level limits. This metric doesn't apply to HTTP connections. |
|
The number of unsubscribe requests that were rejected because the
|
|
The number of unsubscribe requests that were rejected because an internal
error occurred. The |
|
The number of unsubscribe requests that were successfully processed by the
message broker. The |
|
The number of unsubscribe requests that were rejected because the client
exceeded the allowed unsubscribe request rate. The |
Device shadow metrics
Note
The device shadow metrics are displayed in the CloudWatch console under Protocol Metrics.
Metric | Description |
---|---|
|
The number of |
|
The number of |
|
The number of |
|
The number of |
Jobs metrics
Metric | Description |
---|---|
|
The number of job executions whose status has changed to
|
|
The total number of job executions whose status is |
|
The number of client errors generated while executing the job. The
|
|
The number of job executions whose status has changed to |
|
The total number of job executions whose status is |
|
The number of job executions whose status has changed to
|
|
The total number of job executions whose status is |
|
The total number of job executions whose status is |
|
The total number of job executions whose status is |
|
The number of job executions whose status has changed to |
|
The total number of job executions whose status is |
|
The number of job executions whose status has changed to
|
|
The number of job executions whose status has changed to
|
|
The number of server errors generated while executing the job. The
|
|
The number of job executions whose status has changed to
|
|
The total number of job executions whose status is |
Device Defender audit metrics
Metric | Description |
---|---|
|
The number of resources that were found to be noncompliant with a check. The system reports the number of resources that were out of compliance for each check of each audit performed. |
|
The number of resources that were evaluated for compliance. The system reports the number of resources that were evaluated for each check of each audit performed. |
Device Defender detect metrics
Metric | Description |
---|---|
|
The number of metrics exported for a cloud-side, device-side, or custom metric. The system reports the number of metrics exported for the account, for a specific metric. This metric is available only for customers using metrics export. |
|
The number of metrics skipped for a cloud-side, device-side, or custom metric. The system reports the number of metrics skipped for the account, for a specific metric due to insufficient permissions provided to Device Defender Detect to publish to the mqtt topic. This metric is available only for customers using metrics export. |
|
The number of metrics skipped for export for a cloud-side, device-side, or custom metric due to size exceeding MQTT message size constraints. The system reports the number of metrics skipped for export for the account, for a specific metric due to size exceeding MQTT message size constraints. This metric is available only for customers using metrics export. |
|
The number of new violations of security profile behaviors that have been found since the last time an evaluation was performed. The system reports the number of new violations for the account, for a specific security profile, and for a specific behavior of a specific security profile. |
|
The number of violations of security profile behaviors that have been resolved since the last time an evaluation was performed. The system reports the number of resolved violations for the account, for a specific security profile, and for a specific behavior of a specific security profile. |
|
The number of violations of security profile behaviors for which information is no longer available since the last time an evaluation was performed (because the reporting device stopped reporting, or is no longer being monitored for some reason). The system reports the number of invalidated violations for the entire account, for a specific security profile, and for a specific behavior of a specific security profile. |
Device provisioning metrics
Amazon IoT Fleet provisioning metrics | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Metric | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The count of things that have been registered by Fleet Provisioning. While the count is generally accurate, the distributed architecture of Amazon IoT Core makes it difficult to maintain a precise count of registered things. The statistic to use for this metric is:
Dimensions: ClaimCertificateId |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The number of failures that occurred by calls to the
The metric is emitted in both Success (value = 0) and Failure (value = 1) cases. This metric can be used to track the number of certificates created and registered during the CloudWatch-supported aggregation windows, such as 5 min. or 1 hour. The statistics available for this metric are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The number of failures that occurred by calls to the
The metric is emitted in both Success (value = 0) and Failure (value = 1) cases. This metric can be used to track the number of things registered during the CloudWatch-supported aggregation windows, such as 5 min. or 1 hour. The statistics available for this metric are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The number of failures that occurred by calls to the
The metric is emitted in both Success (value = 0) and Failure (value = 1)
cases. This metric can be used to track the number of things registered during
the CloudWatch-supported aggregation windows, such as 5 min. or 1 hour. For the
total number of things registered , see the
The statistics available for this metric are:
Dimensions: TemplateName |
Just-in-time provisioning metrics | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Metric | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The number of times a device failed to provision due to a client error. For example, the policy specified in the template did not exist. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ProvisionThing.ServerError |
The number of times a device failed to provision due to a server error. Customers can retry to provision the device after waiting and they can contact Amazon IoT if the issue remains the same. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ProvisionThing.Success |
The number of times a device was successfully provisioned. |
Fleet indexing metrics
Amazon IoT fleet indexing metrics | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Metric | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
A maximum of 25 named shadows per thing are processed for query terms that
are not data source specific in dynamic thing groups. When this limit is
breached for a thing, the
|
Dimensions for metrics
Metrics use the namespace and provide metrics for the following dimensions | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dimension | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ActionType |
The action type specified by the rule that triggered the request. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The name of the Device Defender Detect security profile behavior that is being monitored. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The name of the Device Defender audit check whose results are being monitored. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The ID of the job whose progress or message connection success/failure is being monitored. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The protocol used to make the request. Valid values are: MQTT or HTTP |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The name of the rule triggered by the request. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The name of the Device Defender scheduled audit whose check results are
being monitored. This has the value |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The name of the Device Defender Detect security profile whose behaviors are being monitored. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The name of the provisioning template. |