Influxdb bad timestamp. In the example, the timestamp is 1465839830100400200...

Influxdb bad timestamp. In the example, the timestamp is 1465839830100400200 (that’s 2016-06-13T17:43:50. Find help, learn solutions, share ideas, and follow discussions. November 2019 14:30:31 but is shown as 14:25 I have imported via API to use seconds as precision but its the same whith nanosecond converted timestamps. With precision=ns, this parses to 2020-08-07 05:50:00 +0000 UTC The bug was reported on 2020-09-20, I'll use that as a proxy for query time In some cases, the bad timestamp error occurs with more general syntax errors in the InfluxDB line protocol. java:19) at retrofit. 1004002Z in RFC3339 format). RuntimeException: bad timestamp at org. Jan 24, 2024 · Insert send a bad timestamp error InfluxDB 1 InfluxQL warhammer73 January 24, 2024, 9:19pm Join us as we explore practical solutions and best practices to fix timestamp-related problems, ensuring your data flows smoothly into InfluxDB. Jul 26, 2019 · In field I have put my timestamp because I don't want Influx DB to set the time_stamp, I wan't to set it. payload) before the input of InfluxDB node (the classic one not the Batch node): Jul 26, 2019 · In field I have put my timestamp because I don't want Influx DB to set the time_stamp, I wan't to set it. psauvftf ppkm rbgrf cimrp gfqy wsaebvc tvcq xusli dslvauc sxvhra