Documentation

range() function

range() filters rows based on time bounds.

Input data must have a _time column of type time. Rows with a null value in the _time are filtered. range() adds a _start column with the value of start and a _stop column with the value of stop. _start and _stop columns are added to the group key. Each input table’s group key value is modified to fit within the time bounds. Tables with all rows outside the time bounds are filtered entirely.

Function type signature
(<-tables: stream[{C with _time: time}], start: A, ?stop: B) => stream[{C with _time: time, _stop: time, _start: time}]
For more information, see Function type signatures.

Parameters

start

(Required) Earliest time to include in results.

Results include rows with _time values that match the specified start time. Use a relative duration, absolute time, or integer (Unix timestamp in seconds). For example, -1h, 2019-08-28T22:00:00Z, or 1567029600. Durations are relative to now().

stop

Latest time to include in results. Default is now().

Results exclude rows with _time values that match the specified stop time. Use a relative duration, absolute time, or integer (Unix timestamp in seconds). For example, -1h, 2019-08-28T22:00:00Z, or 1567029600. Durations are relative to now().

tables

Input data. Default is piped-forward data (<-).

Examples

Query a time range relative to now

from(bucket: "example-bucket")
    |> range(start: -12h)

Query an absolute time range

from(bucket: "example-bucket")
    |> range(start: 2021-05-22T23:30:00Z, stop: 2021-05-23T00:00:00Z)

Query an absolute time range using Unix timestamps

from(bucket: "example-bucket")
    |> range(start: 1621726200, stop: 1621728000)

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: