window() function

window() groups records using regular time intervals.

The function calculates time windows and stores window bounds in the _start and _stop columns. _start and _stop values are assigned to rows based on the row’s _time value.

A single input row may be placed into zero or more output tables depending on the parameters passed into window().

This function is intended to be used when timeColumn (_time by default) is not in the group key. If timeColumn is in the group key, resulting output is confusing and generally not useful.

Window by calendar months and years

every, period, and offset parameters support all valid duration units, including calendar months (1mo) and years (1y).

Window by week

When windowing by week (1w), weeks are determined using the Unix epoch (1970-01-01T00:00:00Z UTC). The Unix epoch was on a Thursday, so all calculated weeks begin on Thursday.

Function type signature
    <-tables: stream[A],
    ?createEmpty: bool,
    ?every: duration,
    ?location: {zone: string, offset: duration},
    ?offset: duration,
    ?period: duration,
    ?startColumn: string,
    ?stopColumn: string,
    ?timeColumn: string,
) => stream[B] where A: Record, B: Record
For more information, see Function type signatures.



Duration of time between windows.


Duration of windows. Default is the every value.

period can be negative, indicating the start and stop boundaries are reversed.


Duration to shift the window boundaries by. Default is 0s.

offset can be negative, indicating that the offset goes backwards in time.


Location used to determine timezone. Default is the location option.


Column that contains time values. Default is _time.


Column to store the window start time in. Default is _start.


Column to store the window stop time in. Default is _stop.


Create empty tables for empty window. Default is false.


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


Window data into 30 second intervals

    |> window(every: 30s)

View example input and output

Window every 20 seconds covering 40 second periods

    |> window(every: 20s, period: 40s)

View example input and output

Window by calendar month

    |> window(every: 1mo)

View example input and output

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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.