Documentation

Work with booleans

A boolean type represents a truth value (true or false).

Type name: bool

Boolean syntax

Boolean literals are represented by the following:

true
false

Convert data types to booleans

Use the bool() function to convert the following basic types to booleans:

  • string: value must be "true" or "false".
  • float: value must be 0.0 (false) or 1.0 (true).
  • int: value must be 0 (false) or 1 (true).
  • uint: value must be 0 (false) or 1 (true).
bool(v: "true")
// Returns true

bool(v: 0.0)
// Returns false

bool(v: 0)
// Returns false

bool(v: uint(v: 1))
// Returns true

Convert columns to booleans

Flux lets you iterate over rows in a stream of tables and convert columns to booleans.

To convert the _value column to booleans, use the toBool() function.

toBool() only operates on the _value column.

data
    |> toBool()
Given the following input data:
_time_value (float)
2021-01-01T00:00:00Z1.0
2021-01-01T02:00:00Z0.0
2021-01-01T03:00:00Z0.0
2021-01-01T04:00:00Z1.0
The example above returns:
_time_value (bool)
2021-01-01T00:00:00Ztrue
2021-01-01T02:00:00Zfalse
2021-01-01T03:00:00Zfalse
2021-01-01T04:00:00Ztrue

To convert any column to booleans:

  1. Use map() to iterate over and rewrite rows.
  2. Use bool() to convert columns values to booleans.
data
    |> map(fn: (r) => ({ r with running: bool(v: r.running) }))
Given the following input data:
_timerunning (int)
2021-01-01T00:00:00Z1
2021-01-01T02:00:00Z0
2021-01-01T03:00:00Z0
2021-01-01T04:00:00Z1
The example above returns:
_timerunning (bool)
2021-01-01T00:00:00Ztrue
2021-01-01T02:00:00Zfalse
2021-01-01T03:00:00Zfalse
2021-01-01T04:00:00Ztrue

Negate boolean values

To negate boolean values, use the not logical operator.

not true
// Returns false

not false
// Returns true

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