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!


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.

Read more

New in InfluxDB 3.4

Key enhancements in InfluxDB 3.4 and the InfluxDB 3 Explorer 1.2.

See the Blog Post

InfluxDB 3.4 is now available for both Core and Enterprise, which introduces offline token generation for use in automated deployments and configurable license type selection that lets you bypass the interactive license prompt. InfluxDB 3 Explorer 1.2 is also available, which includes InfluxDB cache management and other new features.

For more information, check out: