Documentation function 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.



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


(Required) Kafka topic to send data to.


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.


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


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


Time column. Default is _time.


List of tag columns in input data.


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


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


Send data to Kafka

import "kafka"
import "sampledata"
        brokers: [""],
        topic: "example-topic",
        name: "example-metric-name",
        tagColumns: ["tag"],

Was this page helpful?

Thank you for your feedback!

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: