IoT Platform:Enable high-precision, second-level monitoring

Billing

High-precision, second-level monitoring stores monitoring logs in a Log Service (SLS) Logstore. You are charged based on Log Service (SLS) billing standards. For more information, see Billing of Log Service (SLS).

Enable second-level monitoring

1. Log on to the IoT Platform console. In the top navigation bar, select the region where your instance is located.

2. On the Instance Overview tab, click the target instance to go to the Instance Details page.

3. On the Monitoring Reports tab, click the High-precision Second-level Monitoring tab.

4. Click the Second-level Monitoring switch next to the metric you want to monitor, such as Message upstream and downstream TPS or Message forwarding TPS.

5. In the Log Configurations dialog box, complete the steps to enable high-precision, second-level monitoring.

   • If you are enabling high-precision second-level monitoring for the first time, you must first create the corresponding service-linked role and log storage location, and then click Confirm.

     1. If you have not activated Log Service (SLS), click Activate. You are redirected to the activation page. After activating the service, return to the Log Configurations dialog box.

        Click Refresh SLS activation status to confirm that Log Service (SLS) is active.

     2. Click Create next to Role to create the required service-linked roles.

        Role name	Permission policy name	Description	Notes
        AliyunLogETLRole	AliyunLogETLRolePolicy	Authorization policy for the Log Service ETL role. Log Service uses this role by default to access your log resources.	For more information about the AliyunLogETLRole, see Create a scheduled SQL task by using the default role. For the policy content, see AliyunLogETLRolePolicy. For descriptions of the policy elements, see Basic elements of a RAM policy.
        AliyunServiceRoleForIoTLogExport	AliyunServiceRolePolicyForIoTLogExport	Authorization policy for the IoT Platform log export service-linked role. IoT Platform uses this role to access Log Service (SLS) resources.	See Service-linked role for log export.

     3. Click Create next to Log Storage Location.

        • Project: iot-log-${uid}-${regionId}, where ${uid} is your Alibaba Cloud account ID and ${regionId} is the code for the region where your IoT Platform service is deployed.

        • Logstore: iot-second-monitor-logs.

        • MetricStore: iot-second-monitor-metricstore.

        The default retention period for data in the Logstore and metricstore is 7 days.

     After you enable second-level monitoring, the system creates two scheduled SQL tasks in the corresponding Log Service (SLS) project: iot-message-transmit-second-monitor-scheduled-sql and iot-message-second-monitor-scheduled-sql.

   • If this is not the first time you are enabling high-precision, second-level monitoring, Created is displayed next to Role and Log Storage Location. Simply click OK to enable the feature.

6. View instance information and operational data: View the second-level trends for Message upstream and downstream TPS and Message forwarding TPS for your instance.

Disable second-level monitoring

You can disable second-level monitoring for Message upstream and downstream TPS and Message forwarding TPS at any time.

1. Log on to the IoT Platform console. In the top navigation bar, select the region where your instance is located.

2. On the Instance Overview tab, click the target instance to go to the Instance Details page.

3. On the Monitoring Reports tab, click the High-precision Second-level Monitoring tab.

4. Click the Second-level Monitoring switch next to the metric that you want to disable, such as Message upstream and downstream TPS or Message forwarding TPS.

   A confirmation dialog box appears, stating that IoT Platform will stop storing monitoring logs in SLS after you disable the feature. The existing SLS project, Logstore, and metricstore are retained and no further charges are incurred, so you can re-enable the feature later. Click OK.

5. Click OK.

Related documentation

• View instance operational data: View more operational data for your instance, such as data service storage IOPS, the number of online devices.

• Upgrade a public instance to an Enterprise Edition instance or Upgrade an Enterprise Edition instance: If your instance resources are insufficient, for example, if the Message upstream and downstream TPS or Message forwarding TPS is too low, you can upgrade the instance specifications.

• Configure alert rules: Configure alert rules for instance resources to monitor available capacity. Monitoring capacity helps you address resource shortages promptly and prevent disruptions to your device operations.

• Real-time monitoring: You can configure CloudMonitor alert rules, and define threshold-based or event-based rules to monitor IoT Platform device data and network status.