We are excited to announce that Soracom Harvest Data now supports using a time value from the device data as the timestamp for the data stored in Harvest Data.

Data sent from a device to Harvest Data is stored with a timestamp. By default, this timestamp is set according to the time that Harvest Data receives and stores the data. Until now, specifying a custom timestamp has only been possible by including an x-soracom-timestamp custom HTTP header when sending data to Harvest Data.

With this update, you can now configure Harvest Data to set this timestamp according to a time value provided in the device data. This feature allows you to accurately reflect the exact time when your device generated the data, rather than the time the data arrived and was stored by Harvest Data, in order to enable more precise time-series analysis and event tracking.

To utilize this feature, simply specify which JSON key in the data sent by your device contains the timestamp, as well as the timestamp format. For detailed instructions, please refer to the documentation.

Please note: Harvest Data will still support setting a custom timestamp using the x-soracom-timestamp HTTP header. If both the x-soracom-timestamp HTTP header and JSON key are utilized, the timestamp specified in the x-soracom-timestamp HTTP header will take precedence.