:integration: kafka
:plugin: kafka
:type: input
:default_codec: plain
:kafka_client: 3.9.1
:kafka_client_doc: 39

///////////////////////////////////////////
START - GENERATED VARIABLES, DO NOT EDIT!
///////////////////////////////////////////
:version: %VERSION%
:release_date: %RELEASE_DATE%
:changelog_url: %CHANGELOG_URL%
:include_path: ../../../../logstash/docs/include
///////////////////////////////////////////
END - GENERATED VARIABLES, DO NOT EDIT!
///////////////////////////////////////////

[id="plugins-{type}s-{plugin}"]

=== Kafka input plugin

include::{include_path}/plugin_header-integration.asciidoc[]

==== Description

This input will read events from a Kafka topic.

This plugin uses Kafka Client {kafka_client}. For broker compatibility, see the
official
https://cwiki.apache.org/confluence/display/KAFKA/Compatibility+Matrix[Kafka
compatibility reference]. If the linked compatibility wiki is not up-to-date,
please contact Kafka support/community to confirm compatibility.

If you require features not yet available in this plugin (including client
version upgrades), please file an issue with details about what you need.

This input supports connecting to Kafka over:

* SSL (requires plugin version 3.0.0 or later)
* Kerberos SASL (requires plugin version 5.1.0 or later) 

By default security is disabled but can be turned on as needed.

[NOTE]
=======
This plugin does not support using a proxy when communicating to the Kafka broker.  

This plugin does support using a proxy when communicating to the Schema Registry using the <<plugins-{type}s-{plugin}-schema_registry_proxy>> option.
=======

The Logstash Kafka consumer handles group management and uses the default offset management
strategy using Kafka topics.

Logstash instances by default form a single logical group to subscribe to Kafka topics
Each Logstash Kafka consumer can run multiple threads to increase read throughput. Alternatively, 
you could run multiple Logstash instances with the same `group_id` to spread the load across
physical machines. Messages in a topic will be distributed to all Logstash instances with
the same `group_id`.

Ideally you should have as many threads as the number of partitions for a perfect balance --
more threads than partitions means that some threads will be idle

For more information see https://kafka.apache.org/{kafka_client_doc}/documentation.html#theconsumer

Kafka consumer configuration: https://kafka.apache.org/{kafka_client_doc}/documentation.html#consumerconfigs

[id="plugins-{type}s-{plugin}-aws_msk_iam_auth"]
==== AWS MSK IAM authentication
If you use AWS MSK, the AWS MSK IAM access control enables you to handle both authentication and authorization for your MSK cluster with AWS IAM.
For more information on this AWS MSK feature see the https://docs.aws.amazon.com/msk/latest/developerguide/iam-access-control.html[AWS documentation].

To use this Kafka input with AWS MSK IAM authentication, download the uber jar which contains the client library for
this specific cloud vendor and all the transitive dependencies from this https://github.com/elastic/logstash-kafka-iams-packages/releases[repository].
Configure the following setting:
```
security_protocol => "SASL_SSL"
sasl_mechanism => "AWS_MSK_IAM"
sasl_iam_jar_paths => ["/path/to/aws_iam_uber.jar"]
sasl_jaas_config => "software.amazon.msk.auth.iam.IAMLoginModule required;"
sasl_client_callback_handler_class => "software.amazon.msk.auth.iam.IAMClientCallbackHandler"
```
For more IAM authentication configurations, see the https://github.com/aws/aws-msk-iam-auth[AWS MSK IAM authentication library documentation].

==== Metadata fields

The following metadata from Kafka broker are added under the `[@metadata]` field:

* `[@metadata][kafka][topic]`: Original Kafka topic from where the message was consumed.
* `[@metadata][kafka][consumer_group]`: Consumer group
* `[@metadata][kafka][partition]`: Partition info for this message.
* `[@metadata][kafka][offset]`: Original record offset for this message.
* `[@metadata][kafka][key]`: Record key, if any.
* `[@metadata][kafka][timestamp]`: Timestamp in the Record. 
Depending on your broker configuration, this can be
either when the record was created (default) or when it was received by the
broker. See more about property log.message.timestamp.type at
https://kafka.apache.org/{kafka_client_doc}/documentation.html#brokerconfigs

Metadata is only added to the event if the `decorate_events` option is set to `basic` or `extended` (it defaults to `none`).

Please note that `@metadata` fields are not part of any of your events at output time. If you need these information to be 
inserted into your original event, you'll have to use the `mutate` filter to manually copy the required fields into your `event`.

[id="plugins-{type}s-{plugin}-options"]
==== Kafka Input Configuration Options

This plugin supports these configuration options plus the <<plugins-{type}s-{plugin}-common-options>> described later.

NOTE: Some of these options map to a Kafka option. Defaults usually reflect the Kafka default setting,
and might change if Kafka's consumer defaults change.
See the https://kafka.apache.org/{kafka_client_doc}/documentation for more details.

[cols="<,<,<",options="header",]
|=======================================================================
|Setting |Input type|Required
| <<plugins-{type}s-{plugin}-auto_commit_interval_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-auto_create_topics>> |<<boolean,boolean>>|No
| <<plugins-{type}s-{plugin}-auto_offset_reset>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-bootstrap_servers>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-check_crcs>> |<<boolean,boolean>>|No
| <<plugins-{type}s-{plugin}-client_dns_lookup>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-client_id>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-client_rack>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-connections_max_idle_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-consumer_threads>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-decorate_events>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-enable_auto_commit>> |<<boolean,boolean>>|No
| <<plugins-{type}s-{plugin}-exclude_internal_topics>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-fetch_max_bytes>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-fetch_max_wait_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-fetch_min_bytes>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-group_id>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-group_instance_id>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-heartbeat_interval_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-isolation_level>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-jaas_path>> |a valid filesystem path|No
| <<plugins-{type}s-{plugin}-kerberos_config>> |a valid filesystem path|No
| <<plugins-{type}s-{plugin}-key_deserializer_class>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-max_partition_fetch_bytes>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-max_poll_interval_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-max_poll_records>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-metadata_max_age_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-partition_assignment_strategy>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-poll_timeout_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-receive_buffer_bytes>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-reconnect_backoff_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-reconnect_backoff_max_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-request_timeout_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-retry_backoff_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-sasl_client_callback_handler_class>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-sasl_oauthbearer_token_endpoint_url>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-sasl_oauthbearer_scope_claim_name>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-sasl_iam_jar_paths>> |<<array,array>>|No
| <<plugins-{type}s-{plugin}-sasl_login_callback_handler_class>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-sasl_login_connect_timeout_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-sasl_login_read_timeout_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-sasl_login_retry_backoff_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-sasl_login_retry_backoff_max_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-sasl_jaas_config>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-sasl_kerberos_service_name>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-sasl_mechanism>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-schema_registry_key>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-schema_registry_proxy>> |<<uri,uri>>|No
| <<plugins-{type}s-{plugin}-schema_registry_secret>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-schema_registry_ssl_keystore_location>> |a valid filesystem path|No
| <<plugins-{type}s-{plugin}-schema_registry_ssl_keystore_password>> |<<password,password>>|No
| <<plugins-{type}s-{plugin}-schema_registry_ssl_keystore_type>> |<<string,string>>, one of `["jks", "PKCS12"]`|No
| <<plugins-{type}s-{plugin}-schema_registry_ssl_truststore_location>> |a valid filesystem path|No
| <<plugins-{type}s-{plugin}-schema_registry_ssl_truststore_password>> |<<password,password>>|No
| <<plugins-{type}s-{plugin}-schema_registry_ssl_truststore_type>> |<<string,string>>, one of `["jks", "PKCS12"]`|No
| <<plugins-{type}s-{plugin}-schema_registry_url>> |<<uri,uri>>|No
| <<plugins-{type}s-{plugin}-schema_registry_validation>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-security_protocol>> |<<string,string>>, one of `["PLAINTEXT", "SSL", "SASL_PLAINTEXT", "SASL_SSL"]`|No
| <<plugins-{type}s-{plugin}-send_buffer_bytes>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-session_timeout_ms>> |<<number,number>>|No
| <<plugins-{type}s-{plugin}-ssl_endpoint_identification_algorithm>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-ssl_key_password>> |<<password,password>>|No
| <<plugins-{type}s-{plugin}-ssl_keystore_location>> |a valid filesystem path|No
| <<plugins-{type}s-{plugin}-ssl_keystore_password>> |<<password,password>>|No
| <<plugins-{type}s-{plugin}-ssl_keystore_type>> |<<string,string>>, one of `["jks", "PKCS12"]`|No
| <<plugins-{type}s-{plugin}-ssl_truststore_location>> |a valid filesystem path|No
| <<plugins-{type}s-{plugin}-ssl_truststore_password>> |<<password,password>>|No
| <<plugins-{type}s-{plugin}-ssl_truststore_type>> |<<string,string>>, one of `["jks", "PKCS12"]`|No
| <<plugins-{type}s-{plugin}-topics>> |<<array,array>>|No
| <<plugins-{type}s-{plugin}-topics_pattern>> |<<string,string>>|No
| <<plugins-{type}s-{plugin}-value_deserializer_class>> |<<string,string>>|No
|=======================================================================

Also see <<plugins-{type}s-{plugin}-common-options>> for a list of options supported by all
input plugins.

&nbsp;

[id="plugins-{type}s-{plugin}-auto_commit_interval_ms"]
===== `auto_commit_interval_ms` 

  * Value type is <<number,number>>
  * Default value is `5000`.

The frequency in milliseconds that the consumer offsets are committed to Kafka.

[id="plugins-{type}s-{plugin}-auto_offset_reset"]
===== `auto_offset_reset` 

  * Value type is <<string,string>>
  * There is no default value for this setting.

What to do when there is no initial offset in Kafka or if an offset is out of range:

* earliest: automatically reset the offset to the earliest offset
* latest: automatically reset the offset to the latest offset
* none: throw exception to the consumer if no previous offset is found for the consumer's group
* anything else: throw exception to the consumer.

[id="plugins-{type}s-{plugin}-bootstrap_servers"]
===== `bootstrap_servers` 

  * Value type is <<string,string>>
  * Default value is `"localhost:9092"`

A list of URLs of Kafka instances to use for establishing the initial connection to the cluster.
This list should be in the form of `host1:port1,host2:port2` These urls are just used
for the initial connection to discover the full cluster membership (which may change dynamically)
so this list need not contain the full set of servers (you may want more than one, though, in
case a server is down).

[id="plugins-{type}s-{plugin}-check_crcs"]
===== `check_crcs` 

  * Value type is <<boolean,boolean>>
  * Default value is `true`

Automatically check the CRC32 of the records consumed.
This ensures no on-the-wire or on-disk corruption to the messages occurred.
This check adds some overhead, so it may be disabled in cases seeking extreme performance.

[id="plugins-{type}s-{plugin}-client_dns_lookup"]
===== `client_dns_lookup` 

  * Value type is <<string,string>>
  * Default value is `"default"`

How DNS lookups should be done. If set to `use_all_dns_ips`, when the lookup returns multiple 
IP addresses for a hostname, they will all be attempted to connect to before failing the 
connection. If the value is `resolve_canonical_bootstrap_servers_only` each entry will be 
resolved and expanded into a list of canonical names.

[NOTE]
====
Starting from Kafka 3 `default` value for `client.dns.lookup` value has been removed.
If explicitly configured it fallbacks to `use_all_dns_ips`.
====

[id="plugins-{type}s-{plugin}-client_id"]
===== `client_id` 

  * Value type is <<string,string>>
  * Default value is `"logstash"`

The id string to pass to the server when making requests. The purpose of this
is to be able to track the source of requests beyond just ip/port by allowing
a logical application name to be included.

[id="plugins-{type}s-{plugin}-client_rack"]
===== `client_rack` 

  * Value type is <<string,string>>
  * There is no default value for this setting.

A rack identifier for the Kafka consumer. 
Used to select the physically closest rack for the consumer to read from.
The setting corresponds with Kafka's `broker.rack` configuration.

NOTE: Available only for Kafka 2.4.0 and higher. See
https://cwiki.apache.org/confluence/display/KAFKA/KIP-392%3A+Allow+consumers+to+fetch+from+closest+replica[KIP-392].

[id="plugins-{type}s-{plugin}-connections_max_idle_ms"]
===== `connections_max_idle_ms` 

  * Value type is <<number,number>>
  * Default value is `540000` milliseconds (9 minutes).

Close idle connections after the number of milliseconds specified by this config.

[id="plugins-{type}s-{plugin}-consumer_threads"]
===== `consumer_threads` 

  * Value type is <<number,number>>
  * Default value is `1`

Ideally you should have as many threads as the number of partitions for a perfect
balance — more threads than partitions means that some threads will be idle

[id="plugins-{type}s-{plugin}-decorate_events"]
===== `decorate_events` 

  * Value type is <<string,string>>
  * Accepted values are:
    - `none`: no metadata is added
    - `basic`: record's attributes are added
    - `extended`: record's attributes, headers are added (limited to headers with values using UTF-8 encoding)
    - `false`: deprecated alias for `none`
    - `true`: deprecated alias for `basic`
  * Default value is `none`

Option to add Kafka metadata like topic, message size and header key values to the event.
This will add a field named `kafka` to the logstash event containing the following attributes:

* `topic`: The topic this message is associated with
* `consumer_group`: The consumer group used to read in this event
* `partition`: The partition this message is associated with
* `offset`: The offset from the partition this message is associated with
* `key`: A ByteBuffer containing the message key


[id="plugins-{type}s-{plugin}-auto_create_topics"]
===== `auto_create_topics` 

  * Value type is <<boolean,boolean>>
  * Default value is `true`

Controls whether the topic is automatically created when subscribing to a non-existent topic.
A topic will be auto-created only if this configuration is set to `true` and auto-topic creation is enabled on the broker using `auto.create.topics.enable`;
otherwise auto-topic creation is not permitted. 

[id="plugins-{type}s-{plugin}-enable_auto_commit"]
===== `enable_auto_commit` 

  * Value type is <<boolean,boolean>>
  * Default value is `true`

This committed offset will be used when the process fails as the position from
which the consumption will begin.

If true, periodically commit to Kafka the offsets of messages already returned by
the consumer. If value is `false` however, the offset is committed every time the
consumer writes data fetched from the topic to the in-memory or persistent queue.

[id="plugins-{type}s-{plugin}-exclude_internal_topics"]
===== `exclude_internal_topics` 

  * Value type is <<string,string>>
  * There is no default value for this setting.

Whether records from internal topics (such as offsets) should be exposed to the consumer.
If set to true the only way to receive records from an internal topic is subscribing to it.

[id="plugins-{type}s-{plugin}-fetch_max_bytes"]
===== `fetch_max_bytes` 

  * Value type is <<number,number>>
  * Default value is `52428800` (50MB)

The maximum amount of data the server should return for a fetch request. This is not an 
absolute maximum, if the first message in the first non-empty partition of the fetch is larger 
than this value, the message will still be returned to ensure that the consumer can make progress.

[id="plugins-{type}s-{plugin}-fetch_max_wait_ms"]
===== `fetch_max_wait_ms` 

  * Value type is <<number,number>>
  * Default value is `500` milliseconds.

The maximum amount of time the server will block before answering the fetch request if
there isn't sufficient data to immediately satisfy `fetch_min_bytes`. This
should be less than or equal to the timeout used in `poll_timeout_ms`

[id="plugins-{type}s-{plugin}-fetch_min_bytes"]
===== `fetch_min_bytes` 

  * Value type is <<number,number>>
  * There is no default value for this setting.

The minimum amount of data the server should return for a fetch request. If insufficient
data is available the request will wait for that much data to accumulate
before answering the request.

[id="plugins-{type}s-{plugin}-group_id"]
===== `group_id` 

  * Value type is <<string,string>>
  * Default value is `"logstash"`

The identifier of the group this consumer belongs to. Consumer group is a single logical subscriber
that happens to be made up of multiple processors. Messages in a topic will be distributed to all
Logstash instances with the same `group_id`.

NOTE: In cases when multiple inputs are being used in a single pipeline, reading from different topics,
it's essential to set a different `group_id => ...` for each input. Setting a unique `client_id => ...`
is also recommended.

[id="plugins-{type}s-{plugin}-group_instance_id"]
===== `group_instance_id`

* Value type is <<string,string>>
* There is no default value for this setting.

The static membership identifier for this Logstash Kafka consumer. Static membership feature was introduced in
https://cwiki.apache.org/confluence/display/KAFKA/KIP-345%3A+Introduce+static+membership+protocol+to+reduce+consumer+rebalances[KIP-345],
available under Kafka property `group.instance.id`.
Its purpose is to avoid rebalances in situations in which a lot of data
has to be forwarded after a consumer goes offline.
This feature mitigates cases where the service state is heavy and the rebalance of one topic partition from instance
A to B would cause a huge amount of data to be transferred.
A client that goes offline/online frequently can avoid frequent and heavy rebalances by using this option.

NOTE: The `group_instance_id` setting must be unique across all the clients belonging to the same <<plugins-{type}s-{plugin}-group_id>>.
Otherwise, another client connecting with same `group.instance.id` value would cause the oldest instance to be disconnected.
You can set this value to use information such as a hostname, an IP, or anything that uniquely identifies the client application.

NOTE: In cases when multiple threads are configured and `consumer_threads` is greater than one, a suffix is appended to
the `group_instance_id` to avoid collisions.

[id="plugins-{type}s-{plugin}-heartbeat_interval_ms"]
===== `heartbeat_interval_ms` 

  * Value type is <<number,number>>
  * Default value is `3000` milliseconds (3 seconds).

The expected time between heartbeats to the consumer coordinator. Heartbeats are used to ensure 
that the consumer's session stays active and to facilitate rebalancing when new
consumers join or leave the group. The value must be set lower than
`session.timeout.ms`, but typically should be set no higher than 1/3 of that value.
It can be adjusted even lower to control the expected time for normal rebalances.

[id="plugins-{type}s-{plugin}-isolation_level"]
===== `isolation_level` 

  * Value type is <<string,string>>
  * Default value is `"read_uncommitted"`

Controls how to read messages written transactionally. If set to `read_committed`, polling messages will only return
transactional messages which have been committed. If set to `read_uncommitted` (the default), polling messages will
return all messages, even transactional messages which have been aborted. Non-transactional messages will be returned
unconditionally in either mode.

[id="plugins-{type}s-{plugin}-jaas_path"]
===== `jaas_path` 

  * Value type is <<path,path>>
  * There is no default value for this setting.

The Java Authentication and Authorization Service (JAAS) API supplies user authentication and authorization 
services for Kafka. This setting provides the path to the JAAS file. Sample JAAS file for Kafka client:
[source,java]
----------------------------------
KafkaClient {
  com.sun.security.auth.module.Krb5LoginModule required
  useTicketCache=true
  renewTicket=true
  serviceName="kafka";
  };
----------------------------------

Please note that specifying `jaas_path` and `kerberos_config` in the config file will add these  
to the global JVM system properties. This means if you have multiple Kafka inputs, all of them would be sharing the same 
`jaas_path` and `kerberos_config`. If this is not desirable, you would have to run separate instances of Logstash on 
different JVM instances.

[id="plugins-{type}s-{plugin}-kerberos_config"]
===== `kerberos_config` 

  * Value type is <<path,path>>
  * There is no default value for this setting.

Optional path to kerberos config file. This is krb5.conf style as detailed in https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html

[id="plugins-{type}s-{plugin}-key_deserializer_class"]
===== `key_deserializer_class` 

  * Value type is <<string,string>>
  * Default value is `"org.apache.kafka.common.serialization.StringDeserializer"`

Java Class used to deserialize the record's key

[id="plugins-{type}s-{plugin}-max_partition_fetch_bytes"]
===== `max_partition_fetch_bytes` 

  * Value type is <<number,number>>
  * Default value is `1048576` (1MB).

The maximum amount of data per-partition the server will return. The maximum total memory used for a
request will be `#partitions * max.partition.fetch.bytes`. This size must be at least
as large as the maximum message size the server allows or else it is possible for the producer to
send messages larger than the consumer can fetch. If that happens, the consumer can get stuck trying
to fetch a large message on a certain partition.

[id="plugins-{type}s-{plugin}-max_poll_interval_ms"]
===== `max_poll_interval_ms` 

  * Value type is <<number,number>>
  * Default value is `300000` milliseconds (5 minutes).

The maximum delay between invocations of poll() when using consumer group management. This places 
an upper bound on the amount of time that the consumer can be idle before fetching more records. 
If poll() is not called before expiration of this timeout, then the consumer is considered failed and 
the group will rebalance in order to reassign the partitions to another member.

[id="plugins-{type}s-{plugin}-max_poll_records"]
===== `max_poll_records` 

  * Value type is <<number,number>>
  * Default value is `500`.

The maximum number of records returned in a single call to poll().

[id="plugins-{type}s-{plugin}-metadata_max_age_ms"]
===== `metadata_max_age_ms` 

  * Value type is <<number,number>>
  * Default value is `300000` milliseconds (5 minutes).

The period of time in milliseconds after which we force a refresh of metadata even if
we haven't seen any partition leadership changes to proactively discover any new brokers or partitions

[id="plugins-{type}s-{plugin}-partition_assignment_strategy"]
===== `partition_assignment_strategy` 

  * Value type is <<string,string>>
  * There is no default value for this setting.

The name of the partition assignment strategy that the client uses to distribute
partition ownership amongst consumer instances, supported options are:

* `range`
* `round_robin`
* `sticky`
* `cooperative_sticky`

These map to Kafka's corresponding https://kafka.apache.org/{kafka_client_doc}/javadoc/org/apache/kafka/clients/consumer/ConsumerPartitionAssignor.html[`ConsumerPartitionAssignor`]
implementations.

[id="plugins-{type}s-{plugin}-poll_timeout_ms"]
===== `poll_timeout_ms` 

  * Value type is <<number,number>>
  * Default value is `100` milliseconds.

Time Kafka consumer will wait to receive new messages from topics.

After subscribing to a set of topics, the Kafka consumer automatically joins the group when polling.
The plugin poll-ing in a loop ensures consumer liveness.
Underneath the covers, Kafka client sends periodic heartbeats to the server.
The timeout specified the time to block waiting for input on each poll.

[id="plugins-{type}s-{plugin}-receive_buffer_bytes"]
===== `receive_buffer_bytes` 

  * Value type is <<number,number>>
  * Default value is `32768` (32KB).

The size of the TCP receive buffer (SO_RCVBUF) to use when reading data.

[id="plugins-{type}s-{plugin}-reconnect_backoff_ms"]
===== `reconnect_backoff_ms` 

  * Value type is <<number,number>>
  * Default value is `50` milliseconds.

The amount of time to wait before attempting to reconnect to a given host.
This avoids repeatedly connecting to a host in a tight loop.
This backoff applies to all requests sent by the consumer to the broker.

[id="plugins-{type}s-{plugin}-reconnect_backoff_max_ms"]
===== `reconnect_backoff_max_ms`

* Value type is <<number,number>>
* Default value is `1000` milliseconds.

The maximum amount of time in milliseconds to wait when reconnecting to a broker that has repeatedly failed to connect.
If provided, the backoff per host will increase exponentially for each consecutive connection failure, up to this maximum.

[id="plugins-{type}s-{plugin}-request_timeout_ms"]
===== `request_timeout_ms` 

  * Value type is <<number,number>>
  * Default value is `40000` milliseconds (40 seconds).

The configuration controls the maximum amount of time the client will wait
for the response of a request. If the response is not received before the timeout
elapses the client will resend the request if necessary or fail the request if
retries are exhausted.

[id="plugins-{type}s-{plugin}-retry_backoff_ms"]
===== `retry_backoff_ms` 

  * Value type is <<number,number>>
  * Default value is `100` milliseconds.

The amount of time to wait before attempting to retry a failed fetch request
to a given topic partition. This avoids repeated fetching-and-failing in a tight loop.

[id="plugins-{type}s-{plugin}-sasl_client_callback_handler_class"]
===== `sasl_client_callback_handler_class`
  * Value type is <<string,string>>
  * There is no default value for this setting.

The SASL client callback handler class the specified SASL mechanism should use.

[id="plugins-{type}s-{plugin}-sasl_oauthbearer_token_endpoint_url"]
===== `sasl_oauthbearer_token_endpoint_url`
  * Value type is <<string,string>>
  * There is no default value for this setting.

The URL for the OAuth 2.0 issuer token endpoint.

[id="plugins-{type}s-{plugin}-sasl_oauthbearer_scope_claim_name"]
===== `sasl_oauthbearer_scope_claim_name`
  * Value type is <<string,string>>
  * Default value is `"scope"`

(optional) The override name of the scope claim.

[id="plugins-{type}s-{plugin}-sasl_iam_jar_paths"]
===== `sasl_iam_jar_paths`
* Value type is <<array,array>>
* There is no default value for this setting.

Contains the list of paths to jar libraries that contains cloud providers MSK IAM's clients.
There is one jar per provider and can be retrieved as described in <<"plugins-{type}s-{plugin}-aws_msk_iam_auth">>.

[id="plugins-{type}s-{plugin}-sasl_login_callback_handler_class"]
===== `sasl_login_callback_handler_class`
  * Value type is <<string,string>>
  * There is no default value for this setting.

The SASL login callback handler class the specified SASL mechanism should use.

[id="plugins-{type}s-{plugin}-sasl_login_connect_timeout_ms"]
===== `sasl_login_connect_timeout_ms`
  * Value type is <<number,number>>
  * There is no default value for this setting.

(optional) The duration, in milliseconds, for HTTPS connect timeout

[id="plugins-{type}s-{plugin}-sasl_login_read_timeout_ms"]
===== `sasl_login_read_timeout_ms`
  * Value type is <<number,number>>
  * There is no default value for this setting.

(optional) The duration, in milliseconds, for HTTPS read timeout.

[id="plugins-{type}s-{plugin}-sasl_login_retry_backoff_ms"]
===== `sasl_login_retry_backoff_ms`
  * Value type is <<number,number>>
  * Default value is `100` milliseconds.

(optional) The duration, in milliseconds, to wait between HTTPS call attempts.

[id="plugins-{type}s-{plugin}-sasl_login_retry_backoff_max_ms"]
===== `sasl_login_retry_backoff_max_ms`
  * Value type is <<number,number>>
  * Default value is `10000` milliseconds.

(optional) The maximum duration, in milliseconds, for HTTPS call attempts.

[id="plugins-{type}s-{plugin}-sasl_jaas_config"]
===== `sasl_jaas_config` 

  * Value type is <<string,string>>
  * There is no default value for this setting.

JAAS configuration setting local to this plugin instance, as opposed to settings using config file configured using `jaas_path`, which are shared across the JVM. This allows each plugin instance to have its own configuration. 

If both `sasl_jaas_config` and `jaas_path` configurations are set, the setting here takes precedence.

Example (setting for Azure Event Hub):
[source,ruby]
    input {
      kafka {
        sasl_jaas_config => "org.apache.kafka.common.security.plain.PlainLoginModule required username='auser'  password='apassword';"
      }
    }

[id="plugins-{type}s-{plugin}-sasl_kerberos_service_name"]
===== `sasl_kerberos_service_name` 

  * Value type is <<string,string>>
  * There is no default value for this setting.

The Kerberos principal name that Kafka broker runs as. 
This can be defined either in Kafka's JAAS config or in Kafka's config.

[id="plugins-{type}s-{plugin}-sasl_mechanism"]
===== `sasl_mechanism` 

  * Value type is <<string,string>>
  * Default value is `"GSSAPI"`

http://kafka.apache.org/documentation.html#security_sasl[SASL mechanism] used for client connections. 
This may be any mechanism for which a security provider is available.
For AWS MSK IAM authentication use `AWS_MSK_IAM`.
GSSAPI is the default mechanism.

[id="plugins-{type}s-{plugin}-schema_registry_key"]
===== `schema_registry_key`

* Value type is <<string,string>>
* There is no default value for this setting.

Set the username for basic authorization to access remote Schema Registry.

[id="plugins-{type}s-{plugin}-schema_registry_proxy"]
===== `schema_registry_proxy`

* Value type is <<uri,uri>>
* There is no default value for this setting.

Set the address of a forward HTTP proxy. An empty string is treated as if proxy was not set.

[id="plugins-{type}s-{plugin}-schema_registry_secret"]
===== `schema_registry_secret`

* Value type is <<string,string>>
* There is no default value for this setting.

Set the password for basic authorization to access remote Schema Registry.

[id="plugins-{type}s-{plugin}-schema_registry_ssl_keystore_location"]
===== `schema_registry_ssl_keystore_location`

* Value type is <<path,path>>
* There is no default value for this setting.

If schema registry client authentication is required, this setting stores the keystore path.

[id="plugins-{type}s-{plugin}-schema_registry_ssl_keystore_password"]
===== `schema_registry_ssl_keystore_password`

* Value type is <<password,password>>
* There is no default value for this setting.

If schema registry authentication is required, this setting stores the keystore password.

[id="plugins-{type}s-{plugin}-schema_registry_ssl_keystore_type"]
===== `schema_registry_ssl_keystore_type`

* Value type is <<string,string>>
* There is no default value for this setting.

The format of the keystore file. It must be either `jks` or `PKCS12`.

[id="plugins-{type}s-{plugin}-schema_registry_ssl_truststore_location"]
===== `schema_registry_ssl_truststore_location`

* Value type is <<path,path>>
* There is no default value for this setting.

The truststore path to validate the schema registry's certificate.

[id="plugins-{type}s-{plugin}-schema_registry_ssl_truststore_password"]
===== `schema_registry_ssl_truststore_password`

* Value type is <<password,password>>
* There is no default value for this setting.

The schema registry truststore password.

[id="plugins-{type}s-{plugin}-schema_registry_ssl_truststore_type"]
===== `schema_registry_ssl_truststore_type`

* Value type is <<string,string>>
* There is no default value for this setting.

The format of the schema registry's truststore file. It must be either `jks` or `PKCS12`.

[id="plugins-{type}s-{plugin}-schema_registry_url"]
===== `schema_registry_url`

* Value type is <<uri,uri>>

The URI that points to an instance of the
https://docs.confluent.io/current/schema-registry/index.html[Schema Registry] service,
used to manage Avro schemas. Be sure that the Avro schemas for deserializing the data from
the specified topics have been uploaded to the Schema Registry service.
The schemas must follow a naming convention with the pattern <topic name>-value.

Use either the Schema Registry config option or the
<<plugins-{type}s-{plugin}-value_deserializer_class>> config option, but not both.

[id="plugins-{type}s-{plugin}-schema_registry_validation"]
===== `schema_registry_validation`

  * Value can be either of: `auto`, `skip`
  * Default value is `"auto"`

NOTE: Under most circumstances, the default setting of `auto` should not need to be changed.

When using the schema registry, by default the plugin checks connectivity and validates the schema registry, during plugin registration, before events are processed.
In some circumstances, this process may fail when it tries to validate an authenticated schema registry, causing the plugin to crash.
This setting allows the plugin to skip validation during registration, which allows the plugin to continue and events to be processed. Note that an incorrectly configured schema registry will still stop the plugin from processing events.

[id="plugins-{type}s-{plugin}-security_protocol"]
===== `security_protocol` 

  * Value can be any of: `PLAINTEXT`, `SSL`, `SASL_PLAINTEXT`, `SASL_SSL`
  * Default value is `"PLAINTEXT"`

Security protocol to use, which can be either of PLAINTEXT,SSL,SASL_PLAINTEXT,SASL_SSL

[id="plugins-{type}s-{plugin}-send_buffer_bytes"]
===== `send_buffer_bytes` 

  * Value type is <<number,number>>
  * Default value is `131072` (128KB).

The size of the TCP send buffer (SO_SNDBUF) to use when sending data

[id="plugins-{type}s-{plugin}-session_timeout_ms"]
===== `session_timeout_ms` 

  * Value type is <<number,number>>
  * Default value is `10000` milliseconds (10 seconds).

The timeout after which, if the `poll_timeout_ms` is not invoked, the consumer is marked dead
and a rebalance operation is triggered for the group identified by `group_id`

[id="plugins-{type}s-{plugin}-ssl_endpoint_identification_algorithm"]
===== `ssl_endpoint_identification_algorithm`

  * Value type is <<string,string>>
  * Default value is `"https"`

The endpoint identification algorithm, defaults to `"https"`. Set to empty string `""` to disable endpoint verification


[id="plugins-{type}s-{plugin}-ssl_key_password"]
===== `ssl_key_password` 

  * Value type is <<password,password>>
  * There is no default value for this setting.

The password of the private key in the key store file.

[id="plugins-{type}s-{plugin}-ssl_keystore_location"]
===== `ssl_keystore_location` 

  * Value type is <<path,path>>
  * There is no default value for this setting.

If client authentication is required, this setting stores the keystore path.

[id="plugins-{type}s-{plugin}-ssl_keystore_password"]
===== `ssl_keystore_password` 

  * Value type is <<password,password>>
  * There is no default value for this setting.

If client authentication is required, this setting stores the keystore password

[id="plugins-{type}s-{plugin}-ssl_keystore_type"]
===== `ssl_keystore_type` 

  * Value type is <<string,string>>
  * There is no default value for this setting.

The format of the keystore file. It must be either `jks` or `PKCS12`.

[id="plugins-{type}s-{plugin}-ssl_truststore_location"]
===== `ssl_truststore_location` 

  * Value type is <<path,path>>
  * There is no default value for this setting.

The JKS truststore path to validate the Kafka broker's certificate.

[id="plugins-{type}s-{plugin}-ssl_truststore_password"]
===== `ssl_truststore_password` 

  * Value type is <<password,password>>
  * There is no default value for this setting.

The truststore password.

[id="plugins-{type}s-{plugin}-ssl_truststore_type"]
===== `ssl_truststore_type` 

  * Value type is <<string,string>>
  * There is no default value for this setting.

The format of the truststore file. It must be either `jks` or `PKCS12`.

[id="plugins-{type}s-{plugin}-topics"]
===== `topics` 

  * Value type is <<array,array>>
  * Default value is `["logstash"]`

A list of topics to subscribe to, defaults to ["logstash"].

[id="plugins-{type}s-{plugin}-topics_pattern"]
===== `topics_pattern` 

  * Value type is <<string,string>>
  * There is no default value for this setting.

A topic regular expression pattern to subscribe to.

Filtering by a regular expression is done by retrieving the full list of topic names from the broker and applying the pattern locally. When used with brokers with a lot of topics this operation could be very slow, especially if there are a lot of consumers.

NOTE:  When the broker has some topics configured with ACL rules and they miss the DESCRIBE permission, then the subscription
happens but on the broker side it is logged that the subscription of some topics was denied to the configured user.

[id="plugins-{type}s-{plugin}-value_deserializer_class"]
===== `value_deserializer_class` 

  * Value type is <<string,string>>
  * Default value is `"org.apache.kafka.common.serialization.StringDeserializer"`

Java Class used to deserialize the record's value.
A custom value deserializer can be used only if you are not using a Schema Registry.
Use either the value_deserializer_class config option or the
<<plugins-{type}s-{plugin}-schema_registry_url>> config option, but not both.

[id="plugins-{type}s-{plugin}-common-options"]
include::{include_path}/{type}.asciidoc[]

:default_codec!:
