Documentation

integral() function

integral() computes the area under the curve per unit of time of subsequent non-null records.

integral() requires _start and _stop columns that are part of the group key. The curve is defined using _time as the domain and record values as the range.

Function type signature
(
    <-tables: stream[A],
    ?column: string,
    ?interpolate: string,
    ?timeColumn: string,
    ?unit: duration,
) => stream[B] where A: Record, B: Record

For more information, see Function type signatures.

Parameters

unit

Unit of time to use to compute the integral.

column

Column to operate on. Default is _value.

timeColumn

Column that contains time values to use in the operation. Default is _time.

interpolate

Type of interpolation to use. Default is "".

Available interplation types:

  • linear
  • empty string for no interpolation

tables

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

Examples

Calculate the integral

data
    |> integral(unit: 10s)

View example input and output

Calculate the integral with linear interpolation

data
    |> integral(unit: 10s, interpolate: "linear")

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