Documentation

experimental.integral() function

experimental.integral() is subject to change at any time.

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

The curve is defined using _time as the domain and record values as the range.

Input tables must have _start, _stop, _time, and _valuecolumns._startand_stop` must be part of the group key.

Function type signature
(<-tables: stream[{A with _value: B, _time: time}], ?interpolate: string, ?unit: duration) => stream[{A with _value: B}]

For more information, see Function type signatures.

Parameters

unit

Time duration used to compute the integral.

interpolate

Type of interpolation to use. Default is "" (no interpolation).

Use one of the following interpolation options:

  • empty string ("") for no interpolation
  • linear

tables

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

Examples

Calculate the integral

import "experimental"
import "sampledata"

data =
    sampledata.int()
        |> range(start: sampledata.start, stop: sampledata.stop)

data
    |> experimental.integral(unit: 20s)

View example input and output

Calculate the integral with linear interpolation

import "experimental"
import "sampledata"

data =
    sampledata.int()
        |> range(start: sampledata.start, stop: sampledata.stop)

data
    |> experimental.integral(unit: 20s, interpolate: "linear")

View example input and output


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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