Documentation

stateDuration() function

stateDuration() returns the cumulative duration of a given state.

The state is defined by the fn predicate function. For each consecutive record that evaluates to true, the state duration is incremented by the duration of time between records using the specified unit. When a record evaluates to false, the value is set to -1 and the state duration is reset. If the record generates an error during evaluation, the point is discarded, and does not affect the state duration.

The state duration is added as an additional column to each record. The duration is represented as an integer in the units specified.

Note: As the first point in the given state has no previous point, its state duration will be 0.

Function type signature
(
    <-tables: stream[A],
    fn: (r: A) => bool,
    ?column: string,
    ?timeColumn: string,
    ?unit: duration,
) => 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 duration in. Default is stateDuration.

timeColumn

Time column to use to calculate elapsed time between rows. Default is _time.

unit

Unit of time to use to increment state duration. Default is 1s (seconds).

Example units:

  • 1ns (nanoseconds)
  • 1us (microseconds)
  • 1ms (milliseconds)
  • 1s (seconds)
  • 1m (minutes)
  • 1h (hours)
  • 1d (days)

tables

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

Examples

Return the time spent in a specified state

import "sampledata"

sampledata.int()
    |> stateDuration(fn: (r) => r._value < 15)

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: