Documentation

count() function

count() returns the number of records in each input table.

The function counts both null and non-null records.

Empty tables

count() returns 0 for empty tables. To keep empty tables in your data, set the following parameters for the following functions:

Function Parameter
filter() onEmpty: "keep"
window() createEmpty: true
aggregateWindow() createEmpty: true
Function type signature
(<-tables: stream[A], ?column: string) => stream[B] where A: Record, B: Record
For more information, see Function type signatures.

Parameters

column

Column to count values in and store the total count.

tables

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

Examples

Count the number of records in each input table

import "sampledata"

sampledata.string()
    |> count()

Count the number of records with a specific value

  1. Use filter() to filter data by the specific value you want to count.
  2. Use count() to count the number of rows in the table.
import "sampledata"

data =
    sampledata.int()
        |> filter(fn: (r) => r._value > 10)

data
    |> count()

View example input and output


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: