Calculate the moving average

Use movingAverage() or timedMovingAverage() to return the moving average of data.

    |> movingAverage(n: 5)

// OR

    |> timedMovingAverage(every: 5m, period: 10m)


For each row in a table, movingAverage() returns the average of the current value and previous values where n is the total number of values used to calculate the average.

If n = 3:

Row # Calculation
1 Insufficient number of rows
2 Insufficient number of rows
3 (Row1 + Row2 + Row3) / 3
4 (Row2 + Row3 + Row4) / 3
5 (Row3 + Row4 + Row5) / 3

Given the following input:

_time _value
2020-01-01T00:01:00Z 1.0
2020-01-01T00:02:00Z 1.2
2020-01-01T00:03:00Z 1.8
2020-01-01T00:04:00Z 0.9
2020-01-01T00:05:00Z 1.4
2020-01-01T00:06:00Z 2.0

The following would return:

|> movingAverage(n: 3)
_time _value
2020-01-01T00:03:00Z 1.33
2020-01-01T00:04:00Z 1.30
2020-01-01T00:05:00Z 1.36
2020-01-01T00:06:00Z 1.43


For each row in a table, timedMovingAverage() returns the average of the current value and all row values in the previous period (duration). It returns moving averages at a frequency defined by the every parameter.

Each color in the diagram below represents a period of time used to calculate an average and the time a point representing the average is returned. If every = 30m and period = 1h:

0:00 0:30 1:00 1:30 2:00 2:30 3:00 3:00 2:30 2:00 1:30 1:00 0:30

Given the following input:

_time _value
2020-01-01T00:00:00Z 1.0
2020-01-01T00:30:00Z 1.2
2020-01-01T01:00:00Z 1.8
2020-01-01T01:30:00Z 0.9
2020-01-01T02:00:00Z 1.4
2020-01-01T02:30:00Z 2.0
2020-01-01T03:00:00Z 1.9

The following would return:

|> timedMovingAverage(every: 30m, period: 1h)
_time _value
2020-01-01T00:30:00Z 1.0
2020-01-01T01:00:00Z 1.1
2020-01-01T01:30:00Z 1.5
2020-01-01T02:00:00Z 1.35
2020-01-01T02:30:00Z 1.15
2020-01-01T03:00:00Z 1.7
2020-01-01T03:00:00Z 2

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.