Documentation

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.

Parameters

t

(Required) Time threshold for the deadman check.

tables

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

Examples

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

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

data =
    array.from(
        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"])

data
    |> 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!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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