SNMP Trap Source Connector Configuration Properties

To use this connector, specify the name of the connector class in the connector.class configuration property.

connector.class=io.confluent.connect.snmp.SnmpTrapSourceConnector

Connector-specific configuration properties are described below.

Connector

kafka.topic

The Kafka topic name.

  • Type: string
  • Valid Values: Valid topic name (Matches regex [a-zA-Z0-9._-]{1,249})
  • Importance: high
dispatcher.thread.pool.size

Number of threads to allocate for the thread pool. We can increase the value of thread pool size in case we want to speed up the reading/listening of data/pdu/traps from an SNMP device.

  • Type: int
  • Default: 10
  • Valid Values: [1,…,100]
  • Importance: low
snmp.batch.size

Number of records to accumulate in a single batch to kafka. A higher value of dispatcher.thread.pool.size will lead to a large amount of data/pdu/traps ready to be sent to Kafka. Users might need to increase the batch size to increase the throughput.

  • Type: int
  • Default: 1024
  • Valid Values: [1,…,2147483647]
  • Importance: medium
snmp.poll.backoff.ms

Time the connector will sleep if the incoming buffer is empty. CAUTION: Using a high value can block the poll() method to return, and cause the backoff process to fail.

  • Type: long
  • Default: 250
  • Valid Values: [10,…,2147483647]
  • Importance: medium

Auto topic creation

For more information about Auto topic creation, see Configuring Auto Topic Creation for Source Connectors.

Configuration properties accept regular expressions (regex) that are defined as Java regex.

topic.creation.groups

A list of group aliases that are used to define per-group topic configurations for matching topics. A default group always exists and matches all topics.

  • Type: List of String types
  • Default: empty
  • Possible Values: The values of this property refer to any additional groups. A default group is always defined for topic configurations.
topic.creation.$alias.replication.factor

The replication factor for new topics created by the connector. This value must not be larger than the number of brokers in the Kafka cluster. If this value is larger than the number of Kafka brokers, an error occurs when the connector attempts to create a topic. This is a required property for the default group. This property is optional for any other group defined in topic.creation.groups. Other groups use the Kafka broker default value.

  • Type: int
  • Default: n/a
  • Possible Values: >= 1 for a specific valid value or -1 to use the Kafka broker’s default value.
topic.creation.$alias.partitions

The number of topic partitions created by this connector. This is a required property for the default group. This property is optional for any other group defined in topic.creation.groups. Other groups use the Kafka broker default value.

  • Type: int
  • Default: n/a
  • Possible Values: >= 1 for a specific valid value or -1 to use the Kafka broker’s default value.
topic.creation.$alias.include

A list of strings that represent regular expressions that match topic names. This list is used to include topics with matching values, and apply this group’s specific configuration to the matching topics. $alias applies to any group defined in topic.creation.groups. This property does not apply to the default group.

  • Type: List of String types
  • Default: empty
  • Possible Values: Comma-separated list of exact topic names or regular expressions.
topic.creation.$alias.exclude

A list of strings representing regular expressions that match topic names. This list is used to exclude topics with matching values from getting the group’s specfic configuration. $alias applies to any group defined in topic.creation.groups. This property does not apply to the default group. Note that exclusion rules override any inclusion rules for topics.

  • Type: List of String types
  • Default: empty
  • Possible Values: Comma-separated list of exact topic names or regular expressions.
topic.creation.$alias.${kafkaTopicSpecificConfigName}

Any of the Changing Broker Configurations Dynamically for the version of the Kafka broker where the records will be written. The broker’s topic-level configuration value is used if the configuration is not specified for the rule. $alias applies to the default group as well as any group defined in topic.creation.groups.

  • Type: property values
  • Default: Kafka broker value

Listener

snmp.listen.address

IP address to listen for messages on.

  • Type: string
  • Default: 0.0.0.0
  • Importance: low
snmp.listen.port

The port to listen on.

  • Type: int
  • Default: 10161
  • Valid Values: [1,…,65535]
  • Importance: low
snmp.listen.protocol

The Protocol to listen with.

  • Type: string
  • Default: UDP
  • Valid Values: [UDP, TCP]
  • Importance: low

SNMP Security

snmp.v3.enabled

A flag indicating if SNMPv3 protocol is enabled.

  • Type: boolean
  • Default: false
  • Importance: low
v3.security.context.users

A list of SNMPv3 security user names, separated by commas. For example, "myuserA, myuserB".

  • Type: list
  • Default: “”
  • Importance: low

Important

The following security properties are requires for each user name specified in v3.security.context.users. If using Control Center to configure the connector, then these properties need to be added at the bottom under the “Additional Properties” section.

v3.$username.auth.password

Specifies the SNMPv3 authentication passphrase or password. $username applies to any user in the v3.security.context.users list.

  • Type: password
  • Default: [hidden]
  • Importance: low
v3.$username.auth.protocol

Specifies the SNMPv3 authentication protocol or type. This can be set to "" (empty string) or none to use SNMPv3 without authentication. $username applies to any user in the v3.security.context.users list.

  • Type: string
  • Default: md5
  • Valid Values: [“”, none, md5, sha, hmac128sha224, hmac192sha256, hmac256sha384, hmac384sha512]
  • Importance: low
v3.$username.privacy.password

Specifies the SNMPv3 encryption password. $username applies to any user in the v3.security.context.users list.

  • Type: password
  • Default: [hidden]
  • Importance: low
v3.$username.privacy.protocol

Specifies the SNMPv3 privacy/encryption protocol. This can be set to "" (empty string) or none to use SNMPv3 without privacy. $username applies to any user in the v3.security.context.users list.

  • Type: string
  • Default: des
  • Valid Values: [“”, none, des, 3des, aes128, aes192, aes256]
  • Importance: low

V3 enabled connector config example

The following configuration is an example of how to enable V3 with multiple security contexts and how to provide the required security properties.

name=SnmpTrapSourceConnector
tasks.max=1
connector.class=io.confluent.connect.snmp.SnmpTrapSourceConnector
kafka.topic=snmp-kafka-topic
snmp.batch.size=50
snmp.listen.address=0.0.0.0
snmp.listen.port=10161
snmp.v3.enabled=true
v3.security.context.users="myuserA, myuserB"
v3.myuserA.auth.password=<auth-Password>
v3.myuserA.auth.protocol=md5
v3.myuserA.privacy.password=<privacy-password>
v3.myuserA.privacy.protocol=des
v3.myuserB.auth.password=<auth-Password>
v3.myuserB.auth.protocol=md5
v3.myuserB.privacy.password=<privacy-password>
v3.myuserB.privacy.protocol=des

Confluent Platform license

confluent.topic.bootstrap.servers

A list of host/port pairs to use for establishing the initial connection to the Kafka cluster used for licensing. All servers in the cluster will be discovered from the initial connection. This list should be in the form host1:port1,host2:port2,.... These servers are used only 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, in case a server is down.

  • Type: list
  • Importance: high
confluent.topic

Name of the Kafka topic used for Confluent Platform configuration, including licensing information.

  • Type: string
  • Default: _confluent-command
  • Importance: low
confluent.topic.replication.factor

The replication factor for the Kafka topic used for Confluent Platform configuration, including licensing information. This is used only if the topic does not already exist, and the default of 3 is appropriate for production use. If you are using a development environment with less than 3 brokers, you must set this to the number of brokers (often 1).

  • Type: int
  • Default: 3
  • Importance: low

Confluent license properties

You can put license-related properties in the connector configuration, or starting with Confluent Platform version 6.0, you can put license-related properties in the Connect worker configuration instead of in each connector configuration.

This connector is proprietary and requires a license. The license information is stored in the _confluent-command topic. If the broker requires SSL for connections, you must include the security-related confluent.topic.* properties as described below.

confluent.license

Confluent issues enterprise license keys to each subscriber. The license key is text that you can copy and paste as the value for confluent.license. A trial license allows using the connector for a 30-day trial period. A developer license allows using the connector indefinitely for single-broker development environments.

If you are a subscriber, contact Confluent Support for more information.

  • Type: string
  • Default: “”
  • Valid Values: Confluent Platform license
  • Importance: high
confluent.topic.ssl.truststore.location

The location of the trust store file.

  • Type: string
  • Default: null
  • Importance: high
confluent.topic.ssl.truststore.password

The password for the trust store file. If a password is not set access to the truststore is still available, but integrity checking is disabled.

  • Type: password
  • Default: null
  • Importance: high
confluent.topic.ssl.keystore.location

The location of the key store file. This is optional for client and can be used for two-way authentication for client.

  • Type: string
  • Default: null
  • Importance: high
confluent.topic.ssl.keystore.password

The store password for the key store file. This is optional for client and only needed if ssl.keystore.location is configured.

  • Type: password
  • Default: null
  • Importance: high
confluent.topic.ssl.key.password

The password of the private key in the key store file. This is optional for client.

  • Type: password
  • Default: null
  • Importance: high
confluent.topic.security.protocol

Protocol used to communicate with brokers. Valid values are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL.

  • Type: string
  • Default: “PLAINTEXT”
  • Importance: medium

License topic configuration

A Confluent enterprise license is stored in the _confluent-command topic. This topic is created by default and contains the license that corresponds to the license key supplied through the confluent.license property. No public keys are stored in Kafka topics.

The following describes how the default _confluent-command topic is generated under different scenarios:

  • A 30-day trial license is automatically generated for the _confluent command topic if you do not add the confluent.license property or leave this property empty (for example, confluent.license=).
  • Adding a valid license key (for example, confluent.license=<valid-license-key>) adds a valid license in the _confluent-command topic.

Here is an example of the minimal properties for development and testing.

You can change the name of the _confluent-command topic using the confluent.topic property (for instance, if your environment has strict naming conventions). The example below shows this change and the configured Kafka bootstrap server.

confluent.topic=foo_confluent-command
confluent.topic.bootstrap.servers=localhost:9092

The example above shows the minimally required bootstrap server property that you can use for development and testing. For a production environment, you add the normal producer, consumer, and topic configuration properties to the connector properties, prefixed with confluent.topic..

License topic ACLs

The _confluent-command topic contains the license that corresponds to the license key supplied through the confluent.license property. It is created by default. Connectors that access this topic require the following ACLs configured:

  • CREATE and DESCRIBE on the resource cluster, if the connector needs to create the topic.

  • DESCRIBE, READ, and WRITE on the _confluent-command topic.

    Important

    You can also use DESCRIBE and READ without WRITE to restrict access to read-only for license topic ACLs. If a topic exists, the LicenseManager will not try to create the topic.

You can provide access either individually for each principal that will use the license or use a wildcard entry to allow all clients. The following examples show commands that you can use to configure ACLs for the resource cluster and _confluent-command topic.

  1. Set a CREATE and DESCRIBE ACL on the resource cluster:

    kafka-acls --bootstrap-server localhost:9092 --command-config adminclient-configs.conf \
--add --allow-principal User:<principal> \
--operation CREATE --operation DESCRIBE --cluster

  2. Set a DESCRIBE, READ, and WRITE ACL on the _confluent-command topic:

    kafka-acls --bootstrap-server localhost:9092 --command-config adminclient-configs.conf \
--add --allow-principal User:<principal> \
--operation DESCRIBE --operation READ --operation WRITE --topic _confluent-command

Override Default Configuration Properties

You can override the replication factor using confluent.topic.replication.factor. For example, when using a Kafka cluster as a destination with less than three brokers (for development and testing) you should set the confluent.topic.replication.factor property to 1.

You can override producer-specific properties by using the producer.override.* prefix (for source connectors) and consumer-specific properties by using the consumer.override.* prefix (for sink connectors).

You can use the defaults or customize the other properties as well. For example, the confluent.topic.client.id property defaults to the name of the connector with -licensing suffix. You can specify the configuration settings for brokers that require SSL or SASL for client connections using this prefix.

You cannot override the cleanup policy of a topic because the topic always has a single partition and is compacted. Also, do not specify serializers and deserializers using this prefix; they are ignored if added.