Flux range can't find datapoint with _time value within the specified range

Fluxlang
1

I have datapoints with various _time values. One of them has a _time value of 2023-04-15 11:07:12 GMT+2

With a range of

range(
  start: 2023-04-15T10:00:00.000+02:00,
  stop:  2023-04-16T13:00:00.000+02:00
)

I can find it (notice that the stop timestamp is one day later). I can locate the datapoint, and in its _start value it says 2023-04-15 10:00:00 GMT+2, and in its _stop value 2023-04-16 01:00:00 GMT+2

A range of

range(
  start: 2023-04-15T10:00:00.000+02:00,
  stop:  2023-04-15T13:00:00.000+02:00
)

doesn’t. The _stop value of all datapoints is 2023-04-15 01:00:00 GMT+2. It finds datapoints with _time values from 2023-04-15 10:07:14 GMT+2 to 2023-04-15 12:57:14 GMT+2, but the datapoint I am looking for is not there.

Absolutely no clue what’s going on there. The query looks very basic to me. I just filter by _measurement and tags, nothing else. There is no aggregation of some sorts going on in my query that might omit the datapoint.

  1. Why is _stop showing something completely different from my range query?
  2. What could cause the datapoint to go missing
2

so, start and stop values will be always the ones you set as _start and _stop.

the actual timestamp is the _time value.

and _stop value is evaluated as “less than” so if your _time value is as an example: 2023-04-15T13:00:00.000+02:00, it won’t show up. with this range:

range(
start: 2023-04-15T10:00:00.000+02:00,
stop: 2023-04-15T13:00:00.000+02:00
)

because is equal to the _stop value, not less.

I am not sure if this was your issue, but hope It helps.

also, there is a bug on which the time is shown as 12hrs format, so :2023-04-15 01:00:00 GMT+2 is indeed 2023-04-15T13:00:00.000+02:00 (I’ve noticed that on the Influx Data Explorer Interface table view)

3

also, there is a bug on which the time is shown as 12hrs format

Thanks, I already noticed this on _start and _stop in the ui, but your remark made me realize this might be the case for the displayed _time value as well. Turns out the timestamp of my datapoint is not 2023-04-15 11:07:12 GMT+2, but 2023-04-15 23:07:12 GMT+2…