Following is the data in my message.
{
"time_epoch": 1604489437,
"temperature": 100,
"device_id": "TempSensor1"
}
I have an IoT core rule that takes this msg and has an action to send it to the Timestream db table.
In the IoT core rule - I have configured device_id to be the dimension and time_epoch to be the timestamp. Screenshot below:
Problem: When the msg reaches the Timestream db table, the device_id is correctly showing as dimension. The time_epoch is correctly showing under time column. However all 3 - device_id, temperature and time_epoch are getting shown as measures. Screenshot below:
I imagined that - since I have specified in the IoT core rule action that device_id is the dimension and time_epoch is the timestamp, then AWS Timestream should have been smart enough to not include both of these as the measure.
How can I instruct timestream db to not consider device_id and time_epoch as measures; and only consider temperature as the measure? I tried editing the table settings but there I could not find any option to specify/configure the measures.