Available as of Camel 2.13
The Splunk component provides access to Splunk, via the Splunk provided client Rest API, allowing you to publish and search for events in Splunk.
Maven users will need to add the following dependency to their
pom.xml for this component:
Streams data to a named index, or the default index if not specified. When using stream mode be aware that Splunk has some internal buffer (about 1MB or so) before events gets to the index.
If you need realtime, better use
Uses Splunk's Rest API to publish events to a named index, or the default if not specified.
Streams data to a TCP port, and requires a open receiver port in Splunk.
When publishing events the message body should contain a
SplunkEvent. See later.
In this example a converter is required to convert to a
Performs normal search and requires a search query in the search option.
Performs search based on a search query saved in Splunk and requires the name of the query in the
camel-splunk creates a route exchange per search result with an instance of
org.apache.camel.component.splunk.event.SplunkEvent in the body.
Splunk server connection timeout, in milliseconds.
A number that indicates the maximum number of entities to return.
This is not the same as
maxMessagesPerPoll option, which currently is unsupported.
Earliest time of the search time window.
Camel 2.17: Override the default Splunk event host field.
Splunk index to write to.
Initial start offset of the first search. Required.
Latest time of the search time window.
Camel 2.16.0 : Governs whether the body should be inserted as raw.
true, the body will be transformed to a
java.lang.String before it's send to Splunk.
The name of the query saved in Splunk to run.
Scheme to use. Can be one of:
The Splunk query to run.
Splunk source argument.
Splunk sourcetype argument.
Camel 2.16: The SSL protocol to use. Can be one of:
Note: this option is ignored unless the scheme is:
Camel 2.14.0 : Stream exchanges as they are received from Splunk, rather than returning all of them in one batch. This has the benefit of receiving results faster, as well as requiring less memory as exchanges aren't buffered in the component.
Splunk TCP receiver port when using TCP producer endpoint.
true an instance of
sun.net.www.protocol.https.Handler is used to establish the connection to Splunk.
Can be useful when running in application servers to avoid application server HTTPS handling.
Splunk operates on data in key/value pairs. The
SplunkEvent class is a placeholder for such data, and should be in the message body for the producer. Likewise it will be returned in the body per search result for the consumer.
From Camel 2.16.0 you can send raw data to Splunk by setting
raw=true on the producer endpoint. This is useful for e.g.,
json/xml and other payloads where Splunk has build in support.
Search Twitter for tweets with music and publish events to Splunk
To convert a Tweet to a
SplunkEvent you could use a converter like:
Search Splunk for tweets:
Splunk comes with a variety of options for leveraging machine generated data with pre-built apps for analyzing and displaying this. For example the JMX app. could be used to publish JMX attributes, e.g., route and JVM metrics to Splunk, and displaying this on a dashboard.