camel-splunk-hec-kafka-connector sink configuration

When using camel-splunk-hec-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-hec-kafka-connector</artifactId>
  <version>x.x.x</version>
  <!-- use the same version as your Camel Kafka connector version -->
</dependency>

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

Name	Description	Default	Priority
camel.sink.path.splunkURL	Splunk Host URL	null	HIGH
camel.sink.path.token	Splunk authorization token	null	HIGH
camel.sink.endpoint.host	Splunk host.	null	MEDIUM
camel.sink.endpoint.index	Splunk index to write to	"camel"	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	MEDIUM
camel.sink.endpoint.source	Splunk source argument	"camel"	MEDIUM
camel.sink.endpoint.sourceType	Splunk sourcetype argument	"camel"	MEDIUM
camel.sink.endpoint.basicPropertyBinding	Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities	false	MEDIUM
camel.sink.endpoint.synchronous	Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).	false	MEDIUM
camel.sink.endpoint.https	Contact HEC over https.	true	MEDIUM
camel.sink.endpoint.skipTlsVerify	Splunk HEC TLS verification.	false	MEDIUM
camel.component.splunk-hec.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	MEDIUM
camel.component.splunk-hec.basicPropertyBinding	Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities	false	MEDIUM

Name

Description

Default

Priority

camel.sink.path.splunkURL

Splunk Host URL

null

HIGH

camel.sink.path.token

Splunk authorization token

null

HIGH

camel.sink.endpoint.host

Splunk host.

null

MEDIUM

camel.sink.endpoint.index

Splunk index to write to

"camel"

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

MEDIUM

camel.sink.endpoint.source

Splunk source argument

"camel"

MEDIUM

camel.sink.endpoint.sourceType

Splunk sourcetype argument

"camel"

MEDIUM

camel.sink.endpoint.basicPropertyBinding

Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

false

MEDIUM

camel.sink.endpoint.synchronous

Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).

false

MEDIUM

camel.sink.endpoint.https

Contact HEC over https.

true

MEDIUM

camel.sink.endpoint.skipTlsVerify

Splunk HEC TLS verification.

false

MEDIUM

camel.component.splunk-hec.lazyStartProducer

false

MEDIUM

camel.component.splunk-hec.basicPropertyBinding

Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

false

MEDIUM