Documentation

stateCount() function

stateCount() returns the number of consecutive rows in a given state.

The state is defined by the fn predicate function. For each consecutive record that evaluates to true, the state count is incremented. When a record evaluates to false, the value is set to -1 and the state count is reset. If the record generates an error during evaluation, the point is discarded, and does not affect the state count. The state count is added as an additional column to each record.

Function type signature
(<-tables: stream[A], fn: (r: A) => bool, ?column: string) => stream[B] where A: Record, B: Record

For more information, see Function type signatures.

Parameters

fn

(Required) Predicate function that identifies the state of a record.

column

Column to store the state count in. Default is stateCount.

tables

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

Examples

Count the number rows in a specific state

import "sampledata"

sampledata.int()
    |> stateCount(fn: (r) => r._value < 10)

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