Documentation

int() function

int() converts a value to an integer type.

int() behavior depends on the input data type:

Input typeReturned value
stringInteger equivalent of the numeric string
bool1 (true) or 0 (false)
durationNumber of nanoseconds in the specified duration
timeEquivalent nanosecond epoch timestamp
floatValue truncated at the decimal
uintInteger equivalent of the unsigned integer
Function type signature
(v: A) => int

For more information, see Function type signatures.

Parameters

v

(Required) Value to convert.

Examples

Convert basic types to integers

int(v: 10.12)

// Returns 10
int(v: "3")

// Returns 3
int(v: true)

// Returns 1
int(v: 1m)

// Returns 160000000000
int(v: 2022-01-01T00:00:00Z)// Returns 1640995200000000000

Convert all values in a column to integers

If converting the _value column to integer types, use toInt(). If converting columns other than _value, use map() to iterate over each row and int() to convert a column value to a integer type.

data
    |> map(fn: (r) => ({r with exampleCol: int(v: r.exampleCol)}))

View example input and output


Was this page helpful?

Thank you for your feedback!


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