Documentation

movingAverage() function

movingAverage() calculates the mean of non-null values using the current value and n - 1 previous values in the _values column.

Moving average rules

  • The average over a period populated by n values is equal to their algebraic mean.
  • The average over a period populated by only null values is null.
  • Moving averages skip null values.
  • If n is less than the number of records in a table, movingAverage() returns the average of the available values.
Function type signature
(<-tables: stream[{A with _value: B}], n: int) => stream[{A with _value: float}] where B: Numeric

For more information, see Function type signatures.

Parameters

n

(Required) Number of values to average.

tables

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

Examples

Calculate a three point moving average

import "sampledata"  sampledata.int()  |> movingAverage(n: 3)

View example input and output

Calculate a three point moving average with null values

import "sampledata"  sampledata.int(includeNull: true)  |> movingAverage(n: 3)

View example input and output


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2