InfluxDB UDP upload bug?


In our application measurements are uploaded to InfluxDB in batches via the UDP interface, if they meet certain conditions (which are not relevant here).

Today in testing I noticed some odd behavior: a batch of lines whose timestamps are all in the future is silently dropped. A batch whose lines are not all in the future is accepted in its entirety. I’m guessing that the UDP listener looks at the first timestamp in the batch and decides to drop the batch if that timestamp is in the future.

Is this a bug, or is it expected behavior?

Jeremy Begg

By default, points in the future aren’t returned in queries. To query points in the future, you have to specify the time clause to include the future range, e.g. SELECT * FROM m WHERE time > now() AND time < now() + 10m.