Forward data to Time Series Database (TSDB)

Limits

• Data can be forwarded only within a region. For example, you can only forward data from an IoT Platform instance that is deployed in the Japan (Tokyo) region to a TSDB instance that is deployed in the Japan (Tokyo) region.
• You can forward data only to a TSDB instance that is deployed in a VPC.
• You can forward data only in the JSON format.
• Only TSDB is supported. Time Series Database for InfluxDB® and Ganos are not supported.
• In the forwarded messages, all fields are written to TSDB as the metric, except for the fields that are configured as the timestamp and tag value. The data types of the metric parameter support numeric and string. If you use other data types, data may fail to be written to the database.

Create a data destination

1. Log on to the IoT Platform console.
2. On the Overview page, find the instance and click the instance name to go to the Instance Details page.
   Notice Enterprise Edition instances are available only in the Japan (Tokyo) region. If your IoT Platform is not activated in the Japan (Tokyo) region, skip this step.

   
3. In the left-side navigation pane, choose Rules Engine > Data Forwarding.
4. Optional:On the Data Forwarding page, click Go to New Version in the upper-right corner to go to the new version.
   Note If you have performed this step, the Data Forwarding page of the new version appears after you choose Rules > Data Forwarding.
5. Click the Data Destination tab. On this tab, click Create Data Destination.
6. In the Create Data Destination dialog box, enter a data destination name. In this example, enter DataPurpose. Set the parameters and then click OK.

   Parameter	Description
   Select Operation	Select Save to TSDB.
   Region	Specify the region where your IoT Platform instance resides.
   TSDB Instance	Specify the TSDB instance that you have created.
   metric Data Type	Specify the data type of the metric parameter. Valid values: numeric and string. For more information, click the icon.
   Role	Grant IoT Platform the permissions to write data to TSDB.

Configure and start a parser

1. Create a parser named DataParser. For more information, see Create a parser.
2. On the Parser Details page, associate the parser with the created data source.
   1. In the Data Source step of the wizard, click Associate Data Source.
   2. In the dialog box that appears, select DataSource from the Data Source drop-down list, and then click OK.
3. On the Parser Details page, associate the parser with the created data destination.
   1. Click Data Destination in the wizard. In the Data Destination section, click Associate Data Destination.
   2. In the dialog box that appears, select DataPurpose from the Data Destination drop-down list, and then click OK.
   3. In the Data Destination section, view and save the data destination ID. In this example, the ID is 1000.
      When you write the parser script, you must use the data destination ID.
4. On the Parser Details page, click Parser.
5. In the code editor, enter a script. For more information about how to write a script, see Sample script.
   For more information about the function parameters, see Functions.

   // Use the payload() function to obtain the data that is submitted by devices and convert the data by using the JSON format. 
   var data = payload("json");
   // Filter the submitted temperature and humidity values. 
   var h = data.items.Humidity.value;
   var t = data.items.Temperature.value;
   // Forward submitted TSL data. 
   writeTsdb(1000,timestamp(),"temperature", t , {"deviceName":deviceName()});
   writeTsdb(1000,timestamp(),"humidity", h , {"deviceName":deviceName()});

6. Click Debugging. In the dialog box that appears, select a product and a device, specify a topic, and enter payload data to verify whether the script can run properly.
   The following figure shows the parameters.

   The following result indicates that the script is implemented.

   
7. Click Publish.
8. Go to the Parser tab of the Data Forwarding page. Find the DataParser parser and click Start in the Actions column to start the parser.