Documentation

hex.string() function

hex.string() is a user-contributed function maintained by the package author.

hex.string() converts a Flux basic type to a hexadecimal string.

The function is similar to string(), but encodes int, uint, and bytes types to hexadecimal lowercase characters.

Function type signature
(v: A) => string

For more information, see Function type signatures.

Parameters

v

(Required) Value to convert.

Examples

Convert integer to hexadecimal string

import "contrib/bonitoo-io/hex"

hex.string(v: 1234)// Returns 4d2

Convert a boolean to a hexadecimal string value

import "contrib/bonitoo-io/hex"

hex.string(v: true)// Returns "true"

Convert a duration to a hexadecimal string value

import "contrib/bonitoo-io/hex"

hex.string(v: 1m)// Returns "1m"

Convert a time to a hexadecimal string value

import "contrib/bonitoo-io/hex"

hex.string(v: 2021-01-01T00:00:00Z)// Returns "2021-01-01T00:00:00Z"

Convert an integer to a hexadecimal string value

import "contrib/bonitoo-io/hex"

hex.string(v: 1234)// Returns "4d2"

Convert a uinteger to a hexadecimal string value

import "contrib/bonitoo-io/hex"

hex.string(v: uint(v: 5678))// Returns "162e"

Convert a float to a hexadecimal string value

import "contrib/bonitoo-io/hex"

hex.string(v: 10.12)// Returns "10.12"

Convert bytes to a hexadecimal string value

import "contrib/bonitoo-io/hex"

hex.string(v: bytes(v: "Hello world!"))// Returns "48656c6c6f20776f726c6421"

Convert all values in a column to hexadecimal string values

Use map() to iterate over and update all input rows. Use hex.string() to update the value of a column. The following example uses data provided by the sampledata package.

import "sampledata"
import "contrib/bonitoo-io/hex"

data =
    sampledata.int()
        |> map(fn: (r) => ({r with _value: r._value * 1000}))

data
    |> map(fn: (r) => ({r with _value: hex.string(v: r.foo)}))

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