experimental.histogram() function

experimental.histogram() is subject to change at any time.

experimental.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.

Function behavior

  • Outputs a single table for each input table.
  • Each output table represents a unique histogram.
  • Output tables have the same group key as the corresponding input table.
  • Drops columns that are not part of the group key.
  • Adds an le column to store upper bound values.
  • Stores bin counts in the _value column.
Function type signature
(<-tables: stream[{A with _value: float}], bins: [float], ?normalize: bool) => stream[{A with le: float, _value: float}]

For more information, see Function type signatures.



(Required) List of upper bounds to use when computing histogram frequencies, including the maximum value of the data set.

This value can be set to positive infinity (float(v: "+Inf")) if no maximum is known.

Bin helper functions

The following helper functions can be used to generated bins.

  • linearBins()
  • logarithmicBins()


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

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


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


Create a histogram from input data

import "experimental"
import "sampledata"

    |> experimental.histogram(
        bins: [

View example input and output

Was this page helpful?

Thank you for your feedback!

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: