camel-splunk-kafka-connector sink configuration

Connector Description: Publish or search for events in Splunk.

When using camel-splunk-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:

<dependency>
  <groupId>org.apache.camel.kafkaconnector</groupId>
  <artifactId>camel-splunk-kafka-connector</artifactId>
  <version>x.x.x</version>
  <!-- use the same version as your Camel Kafka connector version -->
</dependency>

To use this Sink connector in Kafka connect you’ll need to set the following connector.class

connector.class=org.apache.camel.kafkaconnector.splunk.CamelSplunkSinkConnector

The camel-splunk sink connector supports 22 options, which are listed below.

Name Description Default Required Priority

camel.sink.path.name

Name has no purpose

null

true

HIGH

camel.sink.endpoint.app

Splunk app

null

false

MEDIUM

camel.sink.endpoint.connectionTimeout

Timeout in MS when connecting to Splunk server

5000

false

MEDIUM

camel.sink.endpoint.host

Splunk host.

"localhost"

false

MEDIUM

camel.sink.endpoint.owner

Splunk owner

null

false

MEDIUM

camel.sink.endpoint.port

Splunk port

8089

false

MEDIUM

camel.sink.endpoint.scheme

Splunk scheme

"https"

false

MEDIUM

camel.sink.endpoint.eventHost

Override the default Splunk event host field

null

false

MEDIUM

camel.sink.endpoint.index

Splunk index to write to

null

false

MEDIUM

camel.sink.endpoint.lazyStartProducer

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

false

MEDIUM

camel.sink.endpoint.raw

Should the payload be inserted raw

false

false

MEDIUM

camel.sink.endpoint.source

Splunk source argument

null

false

MEDIUM

camel.sink.endpoint.sourceType

Splunk sourcetype argument

null

false

MEDIUM

camel.sink.endpoint.tcpReceiverLocalPort

Splunk tcp receiver port defined locally on splunk server. (For example if splunk port 9997 is mapped to 12345, tcpReceiverLocalPort has to be 9997)

null

false

MEDIUM

camel.sink.endpoint.tcpReceiverPort

Splunk tcp receiver port

null

false

MEDIUM

camel.sink.endpoint.password

Password for Splunk

null

false

MEDIUM

camel.sink.endpoint.sslProtocol

Set the ssl protocol to use One of: [TLSv1.2] [TLSv1.1] [TLSv1] [SSLv3]

"TLSv1.2"

false

MEDIUM

camel.sink.endpoint.username

Username for Splunk

null

false

MEDIUM

camel.sink.endpoint.useSunHttpsHandler

Use sun.net.www.protocol.https.Handler Https handler to establish the Splunk Connection. Can be useful when running in application servers to avoid app. server https handling.

false

false

MEDIUM

camel.component.splunk.lazyStartProducer

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

false

MEDIUM

camel.component.splunk.autowiredEnabled

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

true

false

MEDIUM

camel.component.splunk.splunkConfigurationFactory

To use the SplunkConfigurationFactory

null

false

MEDIUM

The camel-splunk sink connector has no converters out of the box.

The camel-splunk sink connector has no transforms out of the box.

The camel-splunk sink connector has no aggregation strategies out of the box.

Back to top