The number of messages to send in one batch when using async mode. The producer will wait until either this number of messages are ready to send or queue.buffer.max.ms is reached.

This is for bootstrapping and the producer will only use it for getting metadata (topics, partitions and replicas). The socket connections for sending the actual data will be established based on the broker information returned in the metadata. The format is host1:port1,host2:port2, and the list can be a subset of brokers or a VIP pointing to a subset of brokers.

The client id is a user-specified string sent in each request to help trace calls. It should logically identify the application making the request.

The codec used for output data. Output codecs are a convenient method for encoding your data before it leaves the output, without needing a separate filter in your Logstash pipeline.

This parameter allows you to set whether compression should be turned on for particular topics. If the compression codec is anything other than NoCompressionCodec, enable compression only for specified topics if any. If the list of compressed topics is empty, then enable the specified compression codec for all topics. If the compression codec is NoCompressionCodec, compression is disabled for all topics

This parameter allows you to specify the compression codec for all data generated by this producer. Valid values are none, gzip and snappy.

Only handle events without any of these tags. Optional.

The serializer class for keys (defaults to the same as for messages if nothing is given)

This property will cause the producer to automatically retry a failed send request. This property specifies the number of retries when such failures occur. Note that setting a non-zero value here can lead to duplicates in the case of network errors that cause a message to be sent but the acknowledgement to be lost.

Provides a way to specify a partition key as a string. To specify a partition key for Kafka, configure a format that will produce the key as a string. Defaults key_serializer_class to kafka.serializer.StringEncoder to match. For example, to partition by host:

    output {
      kafka {
          partition_key_format => "%{host}"
      }
    }

The partitioner class for partitioning messages amongst partitions in the topic. The default partitioner is based on the hash of the key. If the key is null, the message is sent to a random partition in the broker. NOTE: topic_metadata_refresh_interval_ms controls how long the producer will distribute to a partition in the topic. This defaults to 10 mins, so the producer will continue to write to a single partition for 10 mins before it switches

This parameter specifies whether the messages are sent asynchronously in a background thread. Valid values are (1) async for asynchronous send and (2) sync for synchronous send. By setting the producer to async we allow batching together of requests (which is great for throughput) but open the possibility of a failure of the client machine dropping unsent data.

The maximum number of unsent messages that can be queued up the producer when using async mode before either the producer must be blocked or data must be dropped.

Maximum time to buffer data when using async mode. For example a setting of 100 will try to batch together 100ms of messages to send at once. This will improve throughput but adds message delivery latency due to the buffering.

The amount of time to block before dropping messages when running in async mode and the buffer has reached queue.buffering.max.messages. If set to 0 events will be enqueued immediately or dropped if the queue is full (the producer send call will never block). If set to -1 the producer will block indefinitely and never willingly drop a send.

This value controls when a produce request is considered completed. Specifically, how many other brokers must have committed the data to their log and acknowledged this to the leader. For more info, see — http://kafka.apache.org/documentation.html#producerconfigs

The amount of time the broker will wait trying to meet the request.required.acks requirement before sending back an error to the client.

Before each retry, the producer refreshes the metadata of relevant topics to see if a new leader has been elected. Since leader election takes a bit of time, this property specifies the amount of time that the producer waits before refreshing the metadata.

Socket write buffer size

The serializer class for messages. The default encoder takes a byte[] and returns the same byte[]

Only handle events with all of these tags. Optional.

The topic to produce the messages to

The producer generally refreshes the topic metadata from brokers when there is a failure (partition missing, leader not available…​). It will also poll regularly (default: every 10min so 600000ms). If you set this to a negative value, metadata will only get refreshed on failure. If you set this to zero, the metadata will get refreshed after each message sent (not recommended). Important note: the refresh happen only AFTER the message is sent, so if the producer never sends a message the metadata is never refreshed

The type to act on. If a type is given, then this output will only act on messages with the same type. See any input plugin’s type attribute for more. Optional.

The number of workers to use for this output. Note that this setting may not be useful for all outputs.