monitor.deadman() function

monitor.deadman() detects when a group stops reporting data. It takes a stream of tables and reports if groups have been observed since time t.

monitor.deadman() retains the most recent row from each input table and adds a dead column. If a record appears after time t, monitor.deadman() sets dead to false. Otherwise, dead is set to true.

Function type signature
(<-tables: stream[{B with _time: C}], t: A) => stream[{B with dead: bool, _time: C}] where A: Comparable, C: Comparable
For more information, see Function type signatures.



(Required) Time threshold for the deadman check.


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


Detect if a host hasn’t reported since a specific time

import "array"
import "influxdata/influxdb/monitor"

data =
        rows: [
            {_time: 2021-01-01T00:00:00Z, host: "a", _value: 1.2},
            {_time: 2021-01-01T00:01:00Z, host: "a", _value: 1.3},
            {_time: 2021-01-01T00:02:00Z, host: "a", _value: 1.4},
            {_time: 2021-01-01T00:03:00Z, host: "a", _value: 1.3},
        |> group(columns: ["host"])

    |> monitor.deadman(t: 2021-01-01T00:05:00Z)

View example input and output

Detect if a host hasn’t reported since a relative time

Use date.add() to return a time value relative to a specified time.

import "influxdata/influxdb/monitor"
import "date"

from(bucket: "example-bucket")
    |> range(start: -10m)
    |> filter(fn: (r) => r._measurement == "example-measurement")
    |> monitor.deadman(t: date.add(d: -5m, to: now()))

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: