Documentation

Query cumulative sum

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

Use the cumulativeSum() function to calculate a running total of values. cumulativeSum sums the values of subsequent records and returns each row updated with the summed total.

Given the following input table:

_time_value
00011
00022
00031
00043

cumulativeSum() returns:

_time_value
00011
00023
00034
00047

The examples below use the example data variable.

Calculate the running total of values
data
  |> cumulativeSum()

Use cumulativeSum() with aggregateWindow()

aggregateWindow() segments data into windows of time, aggregates data in each window into a single point, then removes the time-based segmentation. It is primarily used to downsample data.

aggregateWindow() expects an aggregate function that returns a single row for each time window. To use cumulativeSum() with aggregateWindow, use sum in aggregateWindow(), then calculate the running total of the aggregate values with cumulativeSum().

data
  |> aggregateWindow(every: 5m, fn: sum)
  |> cumulativeSum()

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