1 Answer
- Newest
- Most votes
- Most comments
2
Hi. Your rule is most likely suffering an error. Two ways to check for errors:
- Define an error action for the rule. The easiest error action to use is to republish to another topic, so then you can observe the error in test client.
- Enable AWS IoT logging to CloudWatch, and look for logs of rule action errors: https://docs.aws.amazon.com/iot/latest/developerguide/cwl-format.html#rule-engine-logs
Relevant content
- asked 4 months ago
- asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 9 months ago
I see that you're experiencing difficulties pushing data from the MQTT test console to Timestream despite setting up routing rules. I'm actually facing the same issue. I've watched several videos and followed their steps, but I'm still not seeing any data in Timestream.
I'm wondering if there's an issue with how we're defining the rules or if there could be a problem with the database or table setup on the Timestream side. Have you had any luck troubleshooting this? If you find a solution, I'd greatly appreciate it if you could share it with me.
Thanks,