Important
You are viewing documentation for an older version of Confluent Platform. For the latest, click here.
Configuration Properties¶
To use this connector, specify the name of the connector class in the connector.class
configuration property.
connector.class=io.confluent.connect.syslog.SyslogSourceConnector
Connector-specific configuration properties are described below.
Listener¶
syslog.port
The port to listen on.
- Type: int
- Valid Values: ValidPort{start=1, end=65535}
- Importance: high
syslog.listener
The type of listener to use.
- Type: string
- Default: UDP
- Valid Values: Matches:
TCPSSL
,TCP
,UDP
- Importance: high
syslog.ssl.provider
The SSLContext Provider to use. JDK = JDK’s default implementation. OPENSSL = OpenSSL-based implementation. OPENSSL_REFCNT = OpenSSL-based implementation which does not have finalizers and instead implements ReferenceCounted.
- Type: string
- Default: JDK
- Valid Values: Matches:
JDK
,OPENSSL
,OPENSSL_REFCNT
- Importance: high
syslog.listen.address
The IP Address to listen on.
- Type: string
- Default: 0.0.0.0
- Importance: low
topic
Name of the topic to put all records.
- Type: string
- Default: syslog
- Importance: high
topic.prefix
Deprecated: Use topic
- Type: string
- Default: syslog
- Importance: high
syslog.backoff.millis
The number of milliseconds to wait if there are no messages in the queue for Apache Kafka®.
- Type: int
- Default: 100
- Valid Values: [10,…]
- Importance: low
syslog.queue.batch.size
The number of records to try and retrieve from the buffer.
- Type: int
- Default: 1000
- Valid Values: [0,…,1000000]
- Importance: low
syslog.queue.max.size
The maximum number of records to buffer in the connector. This queue is used as an intermediate before data is written to Kafka.
- Type: int
- Default: 50000
- Valid Values: [0,…,1000000]
- Importance: low
syslog.write.timeout.millis
The number of milliseconds to wait if there are no messages in the queue for Kafka.
- Type: int
- Default: 60000
- Valid Values: [100,…]
- Importance: low
Netty¶
netty.trace.addresses
IP addresses to enable tracing for. If this option is set tracing will only be enabled for the addresses in this list. If empty tracing will be enabled for all addresses.
- Type: list
- Default: “”
- Importance: low
netty.trace.enabled
Flag to enable trace logging at the Netty level. You will need to set io.confluent.connect.syslog.protocol to `TRACE. Keep in mind this will dump anything that comes into the connector to the log.
- Type: boolean
- Default: false
- Importance: low
netty.worker.threads
The number of worker threads for the worker group that processes incoming messages.
- Type: int
- Default: 16
- Valid Values: [1,…,500]
- Importance: low
SSL¶
syslog.ssl.cert.chain.path
Path to X.509 cert chain file in PEM format.
- Type: string
- Default: “”
- Importance: high
syslog.ssl.key.password
The password of the key file(syslog.ssl.key.path), or blank if it’s not password-protected
- Type: password
- Default: [hidden]
- Importance: high
syslog.ssl.key.path
Path to a PKCS#8 private key file in PEM format.
- Type: string
- Default: “”
- Importance: high
syslog.ssl.self.signed.certificate.enable
Flag to determine if a self signed certificate should be generated and used.
- Type: boolean
- Default: false
- Importance: high
TCP¶
syslog.tcp.idle.timeout.secs
The amount of time in seconds to wait before disconnecting an idle session.
- Type: int
- Default: 600
- Valid Values: [0,…]
- Importance: low
Socket¶
netty.event.group.type
The type of event group to use with the Netty listener. EPOLL is only supported on Linux.
- Type: string
- Default: EPOLL
- Valid Values: Matches:
NIO
,EPOLL
- Importance: low
socket.backlog.size
- Type: int
- Default: 1000
- Valid Values: [100,…]
- Importance: low
socket.rcvbuf.bytes
The size of the socket receive buffer in bytes.
- Type: int
- Default: 256000
- Valid Values: [256,…]
- Importance: low
Message Parsing¶
cef.timestamp.mode
The strategy to use when parsing timestamps for CEF formatted messages. The default mode,
header
, looks only in the header.extension_field
looks in a specified extension field key, which is specified in a subconfig.- Type: string
- Default: header
- Valid Values: one of [extension_field, header]
- Importance: low
- Dependents:
cef.timestamp.mode.extension_field.key
cef.timestamp.mode.extension_field.key
The key used to extract timestamps from CEF extension fields.
- Type: string
- Default: “”
- Importance: low
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 <code>host1:port1,host2:port2,…</code>. Since these servers are just used for the initial connection to discover the full cluster membership (which may change dynamically), this list need not contain the full set of servers (you may want more than one, though, 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¶
Note
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, please 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.
Note
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 theconfluent.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.
.
Overriding Default Configuration Properties¶
You can override the replication factor using
confluent.topic.replication.factor
. For example, when using an 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
confluent.topic.producer.
prefix and consumer-specific properties by using
the confluent.topic.consumer.
prefix.
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.