Alert notifications
When your IoT Platform resource usage reaches the value set in an alert rule, an alert is triggered. Alibaba Cloud sends an alert notification to your configured contact group.
Threshold-triggered alert notifications
When a threshold-triggered alert rule is triggered, your contacts receive an email notification similar to the one shown below:
Alert notification content
Field | Description |
IoT Platform instance | Information about the object that triggered the alert. This includes the ProductKey (`productKey`), instance ID (`instanceId`), and region ID (`regionId`) of the product that triggered the alert rule. |
Alert category | The code for the alert category name. This is the alert category that you selected in the threshold-triggered alert rule. For example, `MessageCountForwardedThroughRuleEngine_MNS` corresponds to the category "Number of messages forwarded by the rules engine (MNS)". This means that within a specific period, the number of times the rules engine forwarded data to Simple Message Queue (formerly MNS) (SMQ) exceeded the threshold set in the alert rule. For more information about category name codes, see Threshold-triggered alert categories. |
Alert time | The time when the alert occurred. |
Count | The message volume, number of message forwards, or number of online devices for the monitored category. |
Duration | The duration for which the count exceeded the threshold. |
Rule details | The details of the threshold-triggered alert rule that you set in the Cloud Monitor console. |
Threshold-triggered alert categories
IoT Platform: Basic metrics
Category code | Description |
MessageCountForwardedThroughRuleEngine_DATAHUB | Number of messages forwarded by the rules engine (DATAHUB). This is the number of times the rules engine forwards data to DataHub. |
MessageCountForwardedThroughRuleEngine_FC | Number of messages forwarded by the rules engine (FC). This is the number of times the rules engine forwards data to Function Compute (FC). |
MessageCountForwardedThroughRuleEngine_KAFKA | Number of messages forwarded by the rules engine (KAFKA). This is the number of times the rules engine forwards data to Kafka. |
MessageCountForwardedThroughRuleEngine_LINDORM | Number of messages forwarded by the rules engine (LINDORM). This is the number of times the rules engine forwards data to Lindorm. |
MessageCountForwardedThroughRuleEngine_MNS | Number of messages forwarded by the rules engine (MNS). This is the number of times the rules engine forwards data to Message Service (MNS). |
MessageCountForwardedThroughRuleEngine_MQ | Number of messages forwarded by the rules engine (MQ). This is the number of times the rules engine forwards data to RocketMQ. |
MessageCountForwardedThroughRuleEngine_OTS | Number of messages forwarded by the rules engine (OTS). This is the number of times the rules engine forwards data to Tablestore. |
MessageCountForwardedThroughRuleEngine_RDS | Number of messages forwarded by the rules engine (RDS). This is the number of times the rules engine forwards data to ApsaraDB RDS. |
MessageCountForwardedThroughRuleEngine_REPUBLISH | Number of messages forwarded by the rules engine (REPUBLISH). This is the number of times the rules engine forwards data to other topics in IoT Platform. |
MessageCountForwardedThroughRuleEngine_TSDB | Number of messages forwarded by the rules engine (TSDB). This is the number of times the rules engine forwards data to Time Series Database (TSDB). |
MessageCountSentFromIoT_HTTP_2 | Number of messages sent from the platform (HTTP/2). This is the number of messages sent from the cloud over HTTP/2. |
MessageCountSentFromIoT_LoRa | Number of messages sent from the platform (LoRa). This is the number of messages sent from the cloud over LoRa. |
MessageCountSentFromIoT_MQTT | Number of messages sent from the platform (MQTT). This is the number of messages sent from the cloud over MQTT. |
MessageCountSentToIoT_CoAP | The **Number of messages sent to the platform (CoAP)** metric counts the messages sent from the cloud over the Constrained Application Protocol (CoAP). |
MessageCountSentToIoT_HTTP | Number of messages sent to the platform (HTTP). This is the number of messages that devices send to IoT Platform over HTTP. |
MessageCountSentToIoT_HTTP/2 | Number of messages sent to the platform (HTTP/2). This is the number of messages that devices send to IoT Platform over HTTP/2. |
MessageCountSentToIoT_LoRa | Number of messages sent to the platform (LoRa). This is the number of messages that devices send to IoT Platform over LoRa. |
MessageCountSentToIoT_MQTT | Number of messages sent to the platform (MQTT). This is the number of messages that devices send to IoT Platform over MQTT. |
OnlineDevicesCount_MQTT | Number of real-time online devices (MQTT). This is the number of online devices connected to IoT Platform over MQTT. |
OnlineDevicesCount_HTTP/2 | Number of real-time online devices (HTTP/2). This is the number of online devices connected to IoT Platform over HTTP/2. |
OnlineDeviceInstanceWatermark | A watermark alert for the number of online devices, which is the percentage calculated as: Important This metric applies only to Enterprise instances. If you create a watermark alert for the number of online devices for a public instance, the alert rule is not triggered. |
DeviceEventReportError | Number of failed device event reports. |
DevicePropertyReportError | Number of failed device property reports. |
DevicePropertySettingError | Number of failed device property settings. |
DeviceServiceCallError | Number of failed device service invocations. |
DeviceCount_Product | Number of devices created for a product. |
MessageCountPerMinute | Number of mobile originated and mobile terminated messages per minute for the current instance. |
RuleEngineTransmitCountPerMinute | Number of rules engine forwards per minute for the current instance. |
IoT Platform: Enterprise instances
Category code | Description |
DeviceNum_instance | The number of concurrently online devices. The device usage alert is a percentage calculated as: |
LinkAnalyticsCU | Data processing units (DPUs). |
LinkAnalyticsStorage | Offline storage space. |
MessageWatermarkTps_instance | The transactions per second (TPS) for upstream and downstream messages. This metric is for a watermark alert and is the percentage of |
OtaCommercialUpgradeCount | Alert for the number of valid device upgrades. |
RuleEngineWatermarkTps_instance | Message forwarding TPS. This metric represents the message forwarding TPS watermark. It is calculated as the percentage of |
HotStorageReadIops | Time series storage read IOPS. |
HotStorageWriteIops | Time series storage write IOPS. |
HotStorageCapacity | Time series storage space. |
message_elastic_tps_instance | Alert for the number of elastic mobile originated and mobile terminated messages. |
message_elastic_transmit_instance | Alert for the number of elastic forwarded messages. |
IoT Platform: AMQP consumer groups
Category code | Description |
AMQP_Msg_Accumulate | Number of accumulated messages in the consumer group. |
AMQP_Msg_Consume_rate | Message consumption rate of the consumer group. |
IoT Platform: IoT Digital Twin service
Category code | Description |
dt_data_calculation_dt_instance_tps | Digital twin rule calculation TPS for a digital twin instance. |
dt_data_calculation_tps | Digital twin rule calculation TPS. |
dt_data_forward_dt_instance_tps | Digital twin data forwarding TPS for a digital twin instance. |
dt_data_forward_tps | Digital twin data forwarding TPS. |
dt_data_import_dt_instance_tps | Digital twin data import TPS for a digital twin instance. |
dt_data_import_tps | Digital twin data import TPS. |
Event alert information
When an event-triggered alert rule is triggered, your contacts receive an alert email similar to the following:
Alert message content
Field | Description |
Event name | The code for the alert event name. For example, `Device_Connect_QPM_Limit` indicates that the maximum number of connection requests per minute for a device is reached. For more information, see the Event category description table. |
Alert object | The resource that triggered the alert:
|
Event level | Currently, all events are at the `WARN` (alert) level. |
Event occurrence | The time when the alert event occurred. |
Event status | Currently, the status is always `Fail`. This indicates that subsequent requests failed because the number of connection requests or the message sending Queries Per Second (QPS) reached the upper limit. |
Details | Information about the resource that triggered the alert, in JSON format. This includes the region ID (`regionId`), instance ID (`instanceId`), product `ProductKey` (`productKey`), and device name (`deviceName`). The `productKey` and `deviceName` fields appear only in alerts for when the maximum number of connection requests per minute for a device is reached, or when the mobile originated or mobile terminated message QPS for a device is reached. |
Event category description table
Event name | Description |
Device_Connect_QPM_Limit | The maximum number of connection requests per minute for a device is reached. |
Device_Uplink_QPS_Limit | A single device has reached the QPS limit for mobile originated messages. |
Device_Downlink_QPS_Limit | The Queries Per Second (QPS) for mobile terminated messages to a single device has reached the limit. |
Account_Connect_QPS_Limit | The maximum number of connection requests per second for the current account is reached. |
Account_Uplink_QPS_Limit | The number of publish requests per second for the current account is reached. |
Account_Downlink_QPS_Limit | The number of requests sent to devices per second for the current account is reached. |
Account_RuleEngine_DataForward_QPS_Limit | The number of requests that reach the rules engine per second for the current account is reached. |
intelliBaselineEvent | An intelligent baseline anomaly event. |