If the resource usage of IoT Platform reaches the specified threshold value in an alert rule, an alert is triggered. Then, Alibaba Cloud sends an alert notification to the specified alert group.

Notifications for threshold-triggered alerts

If an alert is triggered based on a threshold-triggered alert rule, alert contacts receive an alert notification email, as shown in the following figure.

Alert notification email
Table 1. Fields of an alert notification email
Log field Description
IoT Platform instance The information about the instance that triggers the alert. The information contains the ProductKey (productKey), instance ID (instanceId), and region ID (regionId).
Metric The code of the metric that you selected when you configured the Rule Description parameter.

In this example, the code MessageCountForwardedThroughRuleEngine_MNS indicates the number of messages that are forwarded by the rules engine. If the number of messages exceeds the specified threshold value in a specified period of time, an alert is triggered.

For more information about the codes of metrics, see Table 2.

Alert time The time when the alert is triggered.
Count The total number of messages, the number of forwarded messages, or the number of connected devices that are counted for the specified metric.
Duration The period of time for which the alert exists.
Rule details The details of the alert rule that you configured in the CloudMonitor console.
Table 2. Metric codes and descriptions
Code Description
MessageCountForwardedThroughRuleEngine_FC The number of messages that are forwarded by the rules engine. It equals the number of times that the rules engine forwards data to Function Compute.
MessageCountForwardedThroughRuleEngine_MNS The number of messages that are forwarded by the rules engine. It equals the number of times that the rules engine forwards data to Message Service (MNS).
MessageCountForwardedThroughRuleEngine_OTS The number of messages that are forwarded by the rules engine. It equals the number of times that the rules engine forwards data to Tablestore.
MessageCountForwardedThroughRuleEngine_RDS The number of messages that are forwarded by the rules engine. It equals the number of times that the rules engine forwards data to ApsaraDB RDS.
MessageCountForwardedThroughRuleEngine_REPUBLISH The number of messages that are forwarded by the rules engine. It equals the number of times that the rules engine forwards data from the current topic to other topics.
MessageCountSentFromIoT_HTTP_2 The number of messages that are sent from IoT Platform by using HTTP/2.
MessageCountSentFromIoT_MQTT The number of messages that are sent from IoT Platform by using Message Queuing Telemetry Transport (MQTT).
MessageCountSentToIoT_CoAP The number of messages that are sent to IoT Platform by using Constrained Application Protocol (CoAP).
MessageCountSentToIoT_HTTP The number of messages that are sent to IoT Platform by using HTTP.
MessageCountSentToIoT_HTTP/2 The number of messages that are sent to IoT Platform by using HTTP/2.
MessageCountSentToIoT_MQTT The number of messages that are sent to IoT Platform by using MQTT.
OnlineDevicesCount_MQTT The number of devices that are connected to IoT Platform by using MQTT in real time.
DeviceEventReportError The number of event reporting failures.
DevicePropertyReportError The number of property reporting failures.
DevicePropertySettingError The number of property setting failures.
DeviceServiceCallError The number of service calling failures.
DeviceNum_instance The percentage of devices that are created for an instance in the IoT Platform console. The value is calculated by using the following formula: Number of devices that are created for the instance in the IoT Platform console/Number of devices that you can create for the instance × 100%.
MessageWatermarkTps_instance The percentage of the current transactions per second (TPS) at which upstream and downstream messages are consumed. The value is calculated by using the following formula: Current TPS at which upstream messages and downstream messages are consumed/Specified TPS at which upstream messages and downstream messages can be consumed when you purchased the instance × 100%.
RuleEngineWatermarkTps_instance The percentage of the current TPS at which the rules engine forwards messages. The value is calculated by using the following formula: Current TPS at which the rules engine forwards messages/Specified TPS at which the rules engine can forward messages when you purchased the instance × 100%.
AMQP_Msg_Accumulate The number of accumulated messages.
AMQP_Msg_Consume_rate The message consumption rate.

Notifications for event alerts

If an alert is triggered based on an event-triggered alert rule, alert contacts receive an alert notification email, as shown in the following figure.

Alert notification email
Table 3. Fields of an alert notification email
Log field Description
Code The code of the event that triggers the alert. In this example, the code Device_Connect_QPM_Limit indicates that the number of connection requests that can be sent per minute by a device has reached the upper limit.

For more information about the codes of events, see Table 4.

Resource The resource that triggers the alert.
  • resourceId: the ID of the resource.

    Format:

    acs:iot:${regionId}::instance/${instanceId}/product/${productKey}/device/${deviceName}
  • Resource name: the ID of the instance. iot-public indicates a public instance.
  • Group ID: the ID of the group to which the device belongs. If the device does not belong to a group, the value of the field is an empty string.
Level All events trigger WARN-level alerts.
Time The time when the event occurs.
Event Status All events are in the Fail state. This state indicates that the subsequent request failed because the number of connection requests that are sent per minute or the number of messages that are sent per second has reached the upper limit.
Description The information about the resource that triggers the alert. The information is in the JSON format. The information contains the region ID (regionId), instance ID (instanceId), ProductKey (productKey), and DeviceName (deviceName). The productKey and deviceName parameters are included in the notification only when the number of connection requests that can be sent per minute, the number of messages that can be sent per second, or the number of messages that can be received per second by a device has reached the upper limit.
Table 4. Event codes
Code Description
Device_Connect_QPM_Limit The number of connection requests that can be sent per minute by a device has reached the upper limit.
Device_Uplink_QPS_Limit The number of messages that can be sent per second by a device has reached the upper limit.
Device_Downlink_QPS_Limit The number of messages that can be received per second by a device has reached the upper limit.
Account_Connect_QPS_Limit The number of connection requests that the current account can send to IoT Platform per second has reached the upper limit.
Account_Uplink_QPS_Limit The number of messages that can be sent per second by the current account has reached the upper limit.
Account_Downlink_QPS_Limit The number of messages that can be received per second by the current account has reached the upper limit.
Account_RuleEngine_DataForward_QPS_Limit The number of messages that can be forwarded per second by the rules engine for the current account has reached the upper limit.