Documentation

histogram() function

histogram() approximates the cumulative distribution of a dataset by counting data frequencies for a list of bins.

A bin is defined by an upper bound where all data points that are less than or equal to the bound are counted in the bin. Bin counts are cumulative.

Each input table is converted into a single output table representing a single histogram. Each output table has the same group key as the corresponding input table. Columns not part of the group key are dropped. Output tables include additional columns for the upper bound and count of bins.

Function type signature
(
    <-tables: stream[A],
    bins: [float],
    ?column: string,
    ?countColumn: string,
    ?normalize: bool,
    ?upperBoundColumn: string,
) => stream[B] where A: Record, B: Record

For more information, see Function type signatures.

Parameters

column

Column containing input values. Column must be of type float. Default is _value.

upperBoundColumn

Column to store bin upper bounds in. Default is le.

countColumn

Column to store bin counts in. Default is _value.

bins

(Required) List of upper bounds to use when computing the histogram frequencies.

Bins should contain a bin whose bound is the maximum value of the data set. This value can be set to positive infinity if no maximum is known.

Bin helper functions

The following helper functions can be used to generated bins.

  • linearBins()
  • logarithmicBins()

normalize

Convert counts into frequency values between 0 and 1. Default is false.

Note: Normalized histograms cannot be aggregated by summing their counts.

tables

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

Examples

Create a cumulative histogram

import "sampledata"

sampledata.float()
    |> histogram(bins: [0.0, 5.0, 10.0, 20.0])

View example input and output

Create a cumulative histogram with dynamically generated bins

import "sampledata"

sampledata.float()
    |> histogram(bins: linearBins(start: 0.0, width: 4.0, count: 3))

View example input and output


Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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