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
  • Copy
  • Fill window

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"],
    )
  • Copy
  • Fill window

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.

Read more

New in InfluxDB 3.2

Key enhancements in InfluxDB 3.2 and the InfluxDB 3 Explorer UI is now generally available.

See the Blog Post

InfluxDB 3.2 is now available for both Core and Enterprise, bringing the general availability of InfluxDB 3 Explorer, a new UI that simplifies how you query, explore, and visualize data. On top of that, InfluxDB 3.2 includes a wide range of performance improvements, feature updates, and bug fixes including automated data retention and more.

For more information, check out: