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!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, 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