Run Logs (Old Version)

Procedure

1. Access IoT Device Access and click Access Console. Click the target instance card.
2. In the navigation pane, choose O&M > Run Logs, and click Configure Run Log.
   Figure 1 Run log - Old version configuration
   

3. In the displayed dialog box, select the service type for data collection and click OK.
   Figure 2 Run log - Log switch of old version configuration
   

4. Create a run log forwarding rule to forward the collected log data to other cloud services, so that you can view and process it. You are advised to forward log data to LTS. The following uses LTS as an example.
   1. In the navigation pane, choose Rules > Data Forwarding, and click Create Rule.
   2. Configure parameters by referring to the following table, and click Create Rule.

      Table 4 Creating a rule

      Parameter	Description
      Rule Name	Specify the name of a rule to create.
      Description	Describe the rule.
      Data Source	Select Run log.
      Trigger	After the data source is selected, the platform automatically matches the trigger event.
      Resource Space	You can select a single resource space or all resource spaces.

   3. Click the Set Forwarding Target tab, and then click Add to set a forwarding target.

      Table 5 Setting the forwarding target

      Parameter	Description
      Forwarding Target	Select Log Tank Service (LTS).
      Region	Currently, log data can be forwarded only to LTS in the same region.
      Log Group/log Stream	Select a log group and log stream of LTS. If no log group or log stream is available, create them by referring to Creating a Log Group and Creating a Log Stream.

      

      Logs are retained in the log group for 7 days by default. Logs that have been stored for more than the retention period will be automatically deleted. For long-term storage, you can transfer logs to Object Storage Service (OBS) buckets. For details, see Transferring Logs to OBS.

      LTS provides a free quota of 500 MB per month. By default, it continues to collect logs when the quota is used up. You will be billed for the excess usage on a pay-per-use basis. You can log in to the LTS console and choose Configuration Center to disable this function.

   4. Click OK, and then click Enable Rule to forward run logs to LTS.

5. Log in to the LTS console and click Log Management.
6. Select the log group and log stream created in 4.c to view the logs reported by IoTDA. Search for raw and target logs by referring to Searching for Logs. For example, search for logs by device ID and service type.
   Figure 3 Run logs - Checking the log list
   
   Figure 4 Run logs - Searching for run logs
   

7. On the log stream details page, click the Log Analysis tab. On the log structuring page that is displayed, select JSON.
   Figure 5 Run logs - Log analysis
   

8. Select a sample log that contains time, device ID, request ID, service type, operation, request parameter, result information, and execution status. Click the button of intelligent extraction to modify the field names, for example, recordTime, requestId, deviceId, categoryName, operation, request, response and result. Change the field type to string. Click Save to complete the log structuring configuration. For details, see Log Structuring.
   Figure 6 Run logs - Configuring log structuring
   

9. After the raw logs are structured, the service will respond. On the Log Management page, select the log group and log stream created in 4.c, and click the button for log analysis to check the structured target logs. You can query logs using SQL statements. For details, see Using SQL Analysis Syntax. For example, to query logs by device ID and service type, run select * where deviceId = '{{deviceId}}' and categoryName = 'device.status'.
   Figure 7 Run logs - Log analysis and search