Documentation

kafka.to() function

kafka.to() sends data to Apache Kafka brokers.

Function type signature
(
    <-tables: stream[A],
    brokers: [string],
    topic: string,
    ?balancer: string,
    ?name: string,
    ?nameColumn: string,
    ?tagColumns: [string],
    ?timeColumn: string,
    ?valueColumns: [string],
) => stream[A] where A: Record

For more information, see Function type signatures.

Parameters

brokers

(Required) List of Kafka brokers to send data to.

topic

(Required) Kafka topic to send data to.

balancer

Kafka load balancing strategy. Default is hash.

The load balancing strategy determines how messages are routed to partitions available on a Kafka cluster. The following strategies are available:

  • hash: Uses a hash of the group key to determine which Kafka partition to route messages to. This ensures that messages generated from rows in the table are routed to the same partition.
  • round-robin: Equally distributes messages across all available partitions.
  • least-bytes: Routes messages to the partition that has received the least amount of data.

name

Kafka metric name. Default is the value of the nameColumn.

nameColumn

Column to use as the Kafka metric name. Default is _measurement.

timeColumn

Time column. Default is _time.

tagColumns

List of tag columns in input data.

valueColumns

List of value columns in input data. Default is ["_value"].

tables

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

Examples

Send data to Kafka

import "kafka"
import "sampledata"

sampledata.int()
    |> kafka.to(
        brokers: ["http://127.0.0.1:9092"],
        topic: "example-topic",
        name: "example-metric-name",
        tagColumns: ["tag"],
    )

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