Documentation

Calculate the moving average

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

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

data
    |> movingAverage(n: 5)

// OR

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

movingAverage()

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
1Insufficient number of rows
2Insufficient 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:00Z1.0
2020-01-01T00:02:00Z1.2
2020-01-01T00:03:00Z1.8
2020-01-01T00:04:00Z0.9
2020-01-01T00:05:00Z1.4
2020-01-01T00:06:00Z2.0

The following would return:

|> movingAverage(n: 3)
_time_value
2020-01-01T00:03:00Z1.33
2020-01-01T00:04:00Z1.30
2020-01-01T00:05:00Z1.36
2020-01-01T00:06:00Z1.43

timedMovingAverage()

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:000:301:001:302:002:303:003:002:302:001:301:000:30

Given the following input:

_time_value
2020-01-01T00:00:00Z1.0
2020-01-01T00:30:00Z1.2
2020-01-01T01:00:00Z1.8
2020-01-01T01:30:00Z0.9
2020-01-01T02:00:00Z1.4
2020-01-01T02:30:00Z2.0
2020-01-01T03:00:00Z1.9

The following would return:

|> timedMovingAverage(every: 30m, period: 1h)
_time_value
2020-01-01T00:30:00Z1.0
2020-01-01T01:00:00Z1.1
2020-01-01T01:30:00Z1.5
2020-01-01T02:00:00Z1.35
2020-01-01T02:30:00Z1.15
2020-01-01T03:00:00Z1.7
2020-01-01T03:00:00Z2

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: