Timeseries timestamps not being returned in queries (original) (raw)

Discussed in #4385

Originally posted by tomscreen May 28, 2026
This is a scenario where it does not look as though full timeseries timestamps are being returned in queries, which is problematic. Am I doing something wrong here? Discussion/comments welcome!

I have a timeseries type set up according to the documentation...

CREATE TIMESERIES TYPE SensorReading TIMESTAMP ts TAGS (deviceId STRING, measureCode STRING) FIELDS (measureValue DOUBLE)

I posted some ILP lines to populate some data...
e.g. SensorReading,deviceId=d123,measureCode=TEMP measureValue=4.985 1779950766233567000

I see data in Studio (see: Screenshot 2026-05-28 at 11.42.34) but weirdly the timestamp just shows as a date.

This is also shown in the JSON view of the results (see: Screenshot 2026-05-28 at 11.44.12).

I thought maybe this is just a Studio issue because in the Timeseries view, I can see data in the chart and in the table under the chart it goes down to the second, which was how the data was written in the first place. (see: Screenshot 2026-05-28 at 11.45.27)

But when I query this data via the HTTP endpoint, all I get is the daily timestamp (see: Screenshot 2026-05-28 at 11.47.20 - part of this has been cut off on purpose so as not to show actual endpoint or username/password, port 2482 is mapped to 2480 on the cluster node I am querying).