Reports
IoTDA provides various dashboards to intuitively present data.
The report on the Overview page collects data by instance. The validity period of the report data is one month. In the navigation pane on the left of the console, choose Overview. The following table describes the names and functions of reports.
Report Name |
Description |
Data Update Frequency |
Available Time Range |
|---|---|---|---|
Registered Devices |
Total number of registered devices of the current instance. |
Every hour |
Hour, day, and month |
Online Devices |
Number of online devices of the current instance. By hour: the maximum number of online devices per hour. By day: the maximum number of online devices per day. |
Every hour |
Hour, day, and month |
Device Messages |
Number of upstream and downstream device messages in the current instance. Upstream device messages include requests of message, property, and event reporting. Downstream device messages include requests of message and command delivery, and property setting and query. |
Every hour |
Hour, day, and month |
User Messages |
Number of user messages in the current instance. User messages mainly include the messages sent from devices to the cloud, and the messages delivered from the cloud to devices. If there are more forwarded messages than messages sent from devices to the cloud, the excess messages are also counted. |
Every hour |
Hour, day, and month |
By default, the O&M reports collect statistics by instance. Click the + icon in the upper right corner of the report to view data of different resource spaces. The validity period of report data is one month.
In the navigation pane of the IoTDA console, choose O&M > Reports. The table below describes the report names and functions.
Report Name |
Description |
Data Update Frequency |
Available Time Range |
|---|---|---|---|
Device Statuses |
Presents the total number of devices, number of online devices, online rate, number of inactive devices, inactive rate, number of offline devices, offline rate, number of abnormal devices, and abnormal rate of the current instance/resource space. |
Every hour |
- |
Device Messages |
Messages reported: the number of messages reported by devices. You can view the data reporting trend and average message reporting rate (messages/second). Device messages: number of upstream and downstream messages. You can call AOM API for querying monitoring data to view detailed data. |
Every hour |
Hour and day |
Commands delivered: number of commands delivered by the platform. |
Every hour |
Hour and day |
|
MQTT Reported Messages TPS |
Maximum number of upstream requests sent by MQTT devices to the platform per second in the current instance. |
Every hour |
10 minutes, 30 minutes, 1 hour, or 1 day |
MQTT Concurrent Connection Setup TPS |
Maximum number of new MQTT connection requests per second in the current instance. |
Every hour |
10 minutes, 30 minutes, 1 hour, or 1 day |
General Device Trends |
Trend of the total number of devices and the number of online devices in the current instance or resource space. |
Every hour |
Hour and day |
Device Online Trends |
Online and offline status of devices in the current instance or resource space, in percentage. |
Every hour |
Hour and day |
Devices by Status |
Number of inactive devices, abnormal devices, and offline devices in the current instance or resource space. |
Every hour |
Hour and day |
Software Upgrade Statuses |
The number of historical software upgrade tasks of all devices of the current instance/resource space, and the number of devices whose upgrades succeeded or failed. |
Every hour |
- |
Firmware Upgrade Statuses |
The number of historical firmware upgrade tasks of all devices of the current instance/resource space, and the number of devices whose upgrades succeeded or failed. |
Every hour |
- |
Device Configuration Statuses |
The number of historical configuration update tasks of all devices of the current instance/resource space, and the number of devices whose updates succeeded or failed. |
Every hour |
- |
For more reports, log in to the AOM console, choose Monitoring > Cloud Service Monitoring, and select IoT Device Access (IoTDA) to view report information. Currently, AOM allows you to view the following IoTDA monitoring information by instance and resource space.
Report Name |
Description |
Data Update Frequency |
Available Time Range |
|---|---|---|---|
Device Status |
Statistics on the number of online, offline, abnormal, and inactive devices in the current instance or resource space. |
Every 10 minutes |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
General Device Trends |
Trends of the total number of devices, number of online devices, and number of offline devices in the current instance or resource space. |
Every 10 minutes |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
Data Transfer Trend |
Trends of AMQP transfers and HTTP message push transfers in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
Data Report Trend |
Trends of the total number of reported NB-IoT data records, MQTT events, MQTT properties, and MQTT messages in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
Report Name |
Description |
Data Update Frequency |
Available Time Range |
|---|---|---|---|
Total Devices |
Trends of the total number of devices, online devices, offline devices, abnormal devices, and inactive devices in the current instance or resource space. |
Every 10 minutes |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
Reported NB Data Records |
Trends of the total number of NB-IoT data reporting times, reporting successes, and reporting failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
Reported MQTT Events |
Trends of the total number of MQTT event reporting times, reporting successes, and reporting failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
Reported MQTT Properties |
Trends of the total number of MQTT property reporting times, reporting successes, and reporting failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
Reported MQTT Messages |
Trends of the total number of MQTT message reporting times, reporting successes, and reporting failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
AMQP Transfers |
Trends of AMQP transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
FunctionGraph Transfers |
Trends of FunctionGraph transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
MRS Kafka Transfers |
Trends of MRS Kafka transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
MQTT Transfers |
Trends of MQTT transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
MySQL Transfers |
Trends of MySQL transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
InfluxDB Transfers |
Trends of InfluxDB transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
HTTP Message Pushes |
Trends of HTTP message push transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
OBS Transfers |
Trends of OBS transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
DMS Kafka Transfers |
Trends of DMS Kafka transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
DIS Transfers |
Trends of DIS transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
ROMA Transfers |
Trends of ROMA Connect transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
LTS Transfers |
Trends of LTS transfers, transfer successes, and transfer failures in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
BCS Huawei Cloud Blockchain Transfers |
Number of BCS Huawei Cloud blockchain transfer times, number of successful BCS Huawei Cloud blockchain transfer times, and number of failed BCS Huawei Cloud blockchain transfer times in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
BCS-Hyperledger Fabric Enhanced Edition Transfers |
Number of BCS-Hyperledger Fabric Enhanced Edition data flows, number of successful BCS-Hyperledger Fabric Enhanced Edition data flows, and number of failed BCS-Hyperledger Fabric Enhanced Edition data flows in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
MongoDB Transfers |
Number of MongoDB data transfer times, number of successful MongoDB data transfer times, and number of failed MongoDB data transfer times in the current instance or resource space. |
Every minute |
1 hour, 6 hours, 12 hours, 1 day, and 7 days |
To obtain report data using an AOM API, see Querying Monitoring Data. For details about custom parameters of IoTDA metrics, see the following tables. In Table 4, namespace corresponds to metrics[].metric.namespace and metricName to metrics[].metric.metricName.
Name |
Description |
Parameter of the AOM API for Querying Monitoring Data |
|---|---|---|
app |
Resource space ID |
metrics[].metric.dimensions[].name |
instance |
Instance ID |
metrics[].metric.dimensions[].name |
taskType |
Task type |
metrics[].metric.dimensions[].name |
Report Name |
Namespace |
MetricName |
|---|---|---|
Total Devices |
IoTDA.DEVICE_STATUS |
Total number of devices: iotda_device_status_totalCount |
Number of online devices: iotda_device_status_onlineCount |
||
Number of offline devices: iotda_device_status_offlineCount |
||
Number of abnormal devices: iotda_device_status_abnormalCount |
||
Number of inactive devices: iotda_device_status_inactiveCount |
||
Reported NB Data Records |
IoTDA.NB_DATA_REPORT |
Total number of reported NB-IoT data records: iotda_south_dataReport_totalCount |
Number of NB-IoT data reporting failures: iotda_south_dataReport_failedCount |
||
Reported MQTT Events |
IoTDA.EVENT_UP |
Total number of MQTT event reporting times: iotda_south_eventUp_totalCount |
Number of MQTT event reporting successes: iotda_south_eventUp_successCount |
||
Number of MQTT event reporting failures: iotda_south_eventUp_failedCount |
||
Reported MQTT Properties |
IoTDA.PROPERTIES_REPORT |
Total number of MQTT property reporting times: iotda_south_propertiesReport_totalCount |
Number of MQTT property reporting successes: iotda_south_propertiesReport_successCount |
||
Number of MQTT property reporting failures: iotda_south_propertiesReport_failedCount |
||
Reported MQTT Messages |
IoTDA.MESSAGE_UP |
Total number of MQTT message reporting times: iotda_south_messageUp_totalCount |
Number of MQTT message reporting successes: iotda_south_messageUp_successCount |
||
Number of MQTT message reporting failures: iotda_south_messageUp_failedCount |
||
AMQP Transfers |
IoTDA.AMQP_FORWARDING |
Total number of AMQP transfers: iotda_amqp_forwarding_totalCount |
Number of AMQP transfer successes: iotda_amqp_forwarding_successCount |
||
Number of AMQP transfer failures: iotda_amqp_forwarding_failedCount |
||
FunctionGraph Transfers |
IoTDA.FUNCTIONGRAPH_FORWARDING |
Total number of FunctionGraph transfers: iotda_functionGraph_forwarding_totalCount |
Number of FunctionGraph transfer successes: iotda_functionGraph_forwarding_successCount |
||
Number of FunctionGraph transfer failures: iotda_functionGraph_forwarding_failedCount |
||
MRS Kafka Transfers |
IoTDA.MRS_KAFKA_FORWARDING |
Total number of MRS Kafka transfers: iotda_mrsKafka_forwarding_totalCount |
Number of MRS Kafka transfer successes: iotda_mrsKafka_forwarding_successCount |
||
Number of MRS Kafka transfer failures: iotda_mrsKafka_forwarding_failedCount |
||
MQTT Transfers |
IoTDA.MQTT_FORWARDING |
Total number of MQTT transfers: iotda_mqtt_forwarding_totalCount |
Number of MQTT transfer successes: iotda_mqtt_forwarding_successCount |
||
Number of MQTT transfer failures: iotda_mqtt_forwarding_failedCount |
||
MySQL Transfers |
IoTDA.MYSQL_FORWARDING |
Total number of MySQL transfers: iotda_mysql_forwarding_totalCount |
Number of MySQL transfer successes: iotda_mysql_forwarding_successCount |
||
Number of MySQL transfer failures: iotda_mysql_forwarding_failedCount |
||
InfluxDB Transfers |
IoTDA.INFLUXDB_FORWARDING |
Total number of InfluxDB transfers: iotda_influxDB_forwarding_totalCount |
Number of InfluxDB transfer successes: iotda_influxDB_forwarding_successCount |
||
Number of InfluxDB transfer failures: iotda_influxDB_forwarding_failedCount |
||
HTTP Message Pushes |
IoTDA.HTTP_FORWARDING |
Total number of HTTP message push transfers: iotda_http_forwarding_totalCount |
Number of HTTP message push transfer successes: iotda_http_forwarding_successCount |
||
Number of HTTP message push transfer failures: iotda_http_forwarding_failedCount |
||
OBS Transfers |
IoTDA.OBS_FORWARDING |
Total number of OBS transfers: iotda_obs_forwarding_totalCount |
Number of OBS transfer successes: iotda_obs_forwarding_successCount |
||
Number of OBS transfer failures: iotda_obs_forwarding_failedCount |
||
DMS Kafka Transfers |
IoTDA.DMS_KAFKA_FORWARDING |
Total number of DMS Kafka transfers: iotda_dmsKafka_forwarding_totalCount |
Number of DMS Kafka transfer successes: iotda_dmsKafka_forwarding_successCount |
||
Number of DMS Kafka transfer failures: iotda_dmsKafka_forwarding_failedCount |
||
DIS Transfers |
IoTDA.DIS_FORWARDING |
Total number of DIS transfers: iotda_dis_forwarding_totalCount |
Number of DIS transfer successes: iotda_dis_forwarding_successCount |
||
Number of DIS transfer failures: iotda_dis_forwarding_failedCount |
||
ROMA Transfers |
IoTDA.ROMA_FORWARDING |
Total number of ROMA Connect transfers: iotda_roma_forwarding_totalCount |
Number of ROMA Connect transfer successes: iotda_roma_forwarding_successCount |
||
Number of ROMA Connect transfer failures: iotda_roma_forwarding_failedCount |
||
LTS Transfers |
IoTDA.LTS_FORWARDING |
Total number of LTS transfers: iotda_lts_forwarding_totalCount |
Number of LTS transfer successes: iotda_lts_forwarding_successCount |
||
Number of LTS transfer failures: iotda_lts_forwarding_failedCount |
||
BCS Huawei Cloud Blockchain Transfers |
IoTDA.BCS_HW_FORWARDING |
Number of BCS Huawei Cloud blockchain transfer times: iotda_bcshw_forwarding_totalCount |
Number of successful BCS Huawei Cloud blockchain transfer times: iotda_bcshw_forwarding_successCount |
||
Number of failed BCS Huawei Cloud blockchain stream transfer times: iotda_bcshw_forwarding_failedCount |
||
BCS-Hyperledger Fabric Enhanced Edition Transfers |
IoTDA.BCS_FABRIC_FORWARDING |
BCS-Hyperledger Fabric Enhanced Edition: iotda_bcsfabric_forwarding_totalCount |
Number of successful stream transfer times of BCS-Hyperledger Fabric Enhanced Edition: iotda_bcsfabric_forwarding_successCount |
||
Number of stream transfer failures of BCS-Hyperledger Fabric Enhanced Edition: iotda_bcsfabric_forwarding_failedCount |
||
MongoDB Transfers |
IoTDA.MONGODB_FORWARDING |
Number of MongoDB transfer times: iotda_mongodb_forwarding_totalCount |
iotda_mongodb_forwarding_successCount: number of successful MongoDB stream transfer times |
||
Number of failed MongoDB stream transfer times: iotda_mongodb_forwarding_failedCount |
||
Software and Firmware Upgrades/Remote Configuration |
AOM.IoTDA |
Number of successes: count: iotda_batchtask_success_count |
Number of failures: iotda_batchtask_failure_count |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
