3 Respuestas
- Más nuevo
- Más votos
- Más comentarios
1
Hi Philipp,
- It is not a bad idea, quite the contrary. By batching the readings from multiple sensors in one single message you are reducing the amount of message considerably
- The IoT Rule Timestream action does not support inserting records with different dimensions (in your case the
sensor_id
would be a dimension), but you can send the message payload to a Lambda function and have the Lambda function write the records in Timestream. You can have a look at this repo on how to write such Lambda function: https://github.com/massi-ang/amazon-timestream-app
0
Regarding the first question, there is no right way to send the data, it all depends on your use case and your expected results. Regarding the second question. Check this tutorial about Ingesting Data into Amazon Timestream with AWS IoT Core.
respondido hace 10 meses
0
It seems to be impossible with just a SQL statement:
See here for more details: https://stackoverflow.com/questions/74090199/aws-iot-rule-sql-republish-get-thing-name-as-json-object-key
respondido hace 10 meses
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
I added a key to my array now:
{ "sensors": [ { "sensor_id": "28-011921dac0de", "value": 58.937 }, { "sensor_id": "28-3ce10457469c", "value": 59.562 }, { "sensor_id": "28-011921d74ee8", "value": 58.0 }, { "sensor_id": "28-3ce104579319", "value": 46.375 } ] }
My SQL query looks like that now: SELECT (SELECT sensor_id, value from sensors) as output FROM 'test/testing'
As a dimension I selected "sensor_id": $(sensor_id) but It is just writing into timestream the string $(sensor_id)
Why?