...
Go to Cloud Monitoring in the Google Cloud console to view Monitoring dashboards or define Monitoring alerts. You can also use query and view device registry metrics using the Cloud Monitoring API to query and view metrics for device registries.
Metrics and resource types
...
Metrics that will be created by IoT Core and be monitored for each registry individually:
Name and |
|---|
label | Kind, |
|---|
type, |
|---|
unit | Description | |
|---|---|---|
|
| The number of devices that have recently sent data to ClearBlade IoT Core. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds. |
e.g., `http`, `mqtt`). | ||
|
| The number of billable bytes transferred by devices. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds. |
e.g., `http`, `mqtt`). |
Data traffic direction (`ingress` or `egress`). | ||
|
| Delta count of errors communicating with devices, grouped by error type. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds. |
Error type, possible options:
|
|
e.g. |
, |
, |
|
). | ||
|
| Delta count of operations performed, grouped by operation type. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds. |
Operation type performed, possible options:
| ||
|
| Delta count of the number of bytes received from devices. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds. |
|
| Delta count of the number of bytes sent to devices. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds |
device/error_count.error:
telemetry_publish_internal
telemetry_publish_user
set_state_internal
set_state_user
incoming_buffer_full
*_internal: Number of events failed because of an internal error.
*_user: Number of events failed because of invalid request, permission denied, or lack of quota.
...
. |
...
event
...
state
...
heartbeat
...
subscribe
...
unsubscribe
...
config_sent
...
config_ack
...
command_sent
...
command_ack
...
connection_open
...