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!


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