The Splunk Software Development Kit for Java
The Splunk Software Development Kit (SDK) for Java contains library code and examples designed to enable developers to build applications using Splunk.
Splunk is a search engine and analytic environment that uses a distributed map-reduce architecture to efficiently index, search and process large time-varying data sets.
The Splunk product is popular with system administrators for aggregation and monitoring of IT machine data, security, compliance and a wide variety of other scenarios that share a requirement to efficiently index, search, analyze and generate real-time notifications from large volumes of time series data.
The Splunk developer platform enables developers to take advantage of the same technology used by the Splunk product to build exciting new applications that are enabled by Splunk's unique capabilities.
Getting started with the Splunk SDK for Java
The Splunk SDK for Java contains library code and examples that show how to programmatically interact with Splunk for a variety of scenarios including searching, saved searches, data inputs, and many more, along with building complete applications.
The information in this Readme provides steps to get going quickly, but for more in-depth information be sure to visit the Splunk Developer Portal.
Here's what you need to get going with the Splunk SDK for Java.
Splunk SDK for Java
Get the Splunk SDK for Java—download the SDK as a ZIP, then extract the files and build the SDK. Or, download the JAR and add it to your project.
If you want to contribute to the SDK, clone the repository from GitHub.
Java and Ant
You'll need Java SE version 6 or higher, which you can download from the Oracle web site.
You'll also need Ant, which you can install from the Apache website.
The Splunk SDK for Java is compatible with Java 8. Be aware that Java 8 disables Secure Sockets Layer version 3 (SSLv3) by default, so you will need to use Transport Layer Security (TLS) instead. To see an example of how to do this, see the
ssl_protocols example. Alternatively, you can re-enable SSLv3 in Java settings, but this is not recommended.
If you are using Windows, you'll need to make sure the following system variables are created and set:
ANT_HOME should be set to the location where Ant is installed.
JAVA_HOME should be set to the directory where the JDK is installed.
PATH should include the path to the %ANT_HOME%\bin directory.
For full installation instructions, you can find more information here:
You can use Apache Maven to build your Splunk SDK for Java projects. With a few updates to your project's
pom.xml file, it will retrieve all necessary dependencies and seamlessly build your project.
To add the Splunk SDK for Java
.JAR file as a dependency:
- Add the repository to your project's
<repositories> ... <repository> <id>splunk-artifactory</id> <name>Splunk Releases</name> <url>http://splunk.jfrog.io/splunk/ext-releases-local</url> </repository> </repositories>
- Add the dependency to the
<dependencies> ... <dependency> <groupId>com.splunk</groupId> <artifactId>splunk</artifactId> <version>220.127.116.11</version> </dependency> </dependencies>
Be sure to update the version number to match the version of the Splunk SDK for Java that you are using.
Building the SDK and documentation
To build the SDK, open a command prompt in the /splunk-sdk-java directory and enter:
This command builds all of the .class and .jar files. If you just want to build the .class files, enter:
To remove all build artifacts from the repository, enter:
To build the documentation for the SDK, enter:
Examples and unit tests
The Splunk SDK for Java includes several examples and unit tests that are run at the command line.
Set up the .splunkrc file
To connect to Splunk, many of the SDK examples and unit tests take command-line arguments that specify values for the host, port, and login credentials for Splunk. For convenience during development, you can store these arguments as key-value pairs in a text file named .splunkrc. Then, the SDK examples and unit tests use the values from the .splunkrc file when you don't specify them.
To use this convenience file, create a text file with the following format:
# Splunk host (default: localhost) host=localhost # Splunk admin port (default: 8089) port=8089 # Splunk username username=admin # Splunk password password=changeme # Access scheme (default: https) scheme=https # Your version of Splunk (default: 5.0) version=5.0
Save the file as .splunkrc in the current user's home directory.
For example, on Mac OS X, save the file as:
On Windows, save the file as:
You might get errors in Windows when you try to name the file because ".splunkrc" looks like a nameless file with an extension. You can use the command line to create this file—go to the C:\Users\currentusername directory and enter the following command:
Click Yes, then continue creating the file.
Note: Storing login credentials in the .splunkrc file is only for convenience during development. This file isn't part of the Splunk platform and shouldn't be used for storing user credentials for production. And, if you're at all concerned about the security of your credentials, just enter them at the command line rather than saving them in this file.
After you build the SDK, examples are put in the /splunk-sdk-
java/dist/examples directory. To run the examples, run the Java interpreter
at the command line using the
-jar flag to specify the target example jar
file, and include any arguments that are required by the example. To get help
for an example, use the
--help argument with an example.
For example, to see the command-line arguments for the Search example, open a command prompt in the /splunk-sdk-java directory and enter:
java -jar dist/examples/search.jar --help
To run the Search example, open a command prompt in the /splunk-sdk-java directory and enter:
java -jar dist/examples/search.jar "search * | head 10" --output_mode=csv
There is also a helper script called run in the root of the repository that simplifies running the SDK examples. For example, on Mac OS X you could simply enter:
./run search "search * | head 10" --output_mode=csv
All the the example jars are completely self contained. They can be used completely independently of the SDK's repository.
Run unit tests
To run the SDK unit tests, open a command prompt in the /splunk-sdk-java directory and enter:
To run the units from anywhere in the repository, enter:
ant test -find
You can also run specific test classes by passing the class to the -Dtestcase= option, e.g.,
ant test -Dtestcase=AtomFeedTest
The ant configuration can also produce a single HTML report of all the tests run using the target testreport (which also understands the -Dtestcase= option), e.g.
The report will be written in build/reports/tests/index.html.
It's also possible to run the units within Java IDEs such as IntelliJ and Eclipse. For example, to open the Splunk SDK for Java project in Eclipse:
- Click File, Import.
- Click General, Existing Projects into Workspace, then click Next.
- In Select root directory, type the path to the Splunk SDK for Java root directory (or click Browse to locate it), then click Finish.
Measure code coverage
To measure the code coverage of the test suite, open a command prompt in the /splunk-sdk-java directory and enter:
To run code coverage from anywhere in the repository, enter:
ant coverage -find
To view the coverage report, open /splunk-sdk-java/build/reports/coverage/index.html in your web browser.
|/argsGenerator||This directory is created by the build and contains intermediate build ouputs|
|/build||This directory is created by the build and contains intermediate build ouputs|
|/dist||This directory is created by the build and contains final build outputs|
|/examples||Examples demonstrating various SDK features|
|/lib||Third-party libraries used by examples and unit tests|
|/tests||Source for unit tests|
|/util||Utilities shared by examples and units|
The CHANGELOG.md file in the root of the repository contains a description of changes for each version of the SDK. You can also find it online at https://github.com/splunk/splunk-sdk-java/blob/master/CHANGELOG.md.
The master branch always represents a stable and released version of the SDK. You can read more about our branching model on our Wiki at https://github.com/splunk/splunk-sdk-java/wiki/Branching-Model.
Documentation and resources
If you need to know more:
For all things developer with Splunk, your main resource is the Splunk Developer Portal.
For conceptual and how-to documentation, see the Overview of the Splunk SDK for Java.
For API reference documentation, see the Splunk SDK for Java Reference.
For more about the Splunk REST API, see the REST API Reference.
For more about about Splunk in general, see Splunk>Docs.
For more about this SDK's repository, see our GitHub Wiki.
Stay connected with other developers building on Splunk.
How to contribute
If you would like to contribute to the SDK, go here for more information:
You can still request assistance using the following options:
Post questions to Splunk Answers. Be sure to use tags to identify the SDK or tool you are having an issue with.
File an issue on GitHub.
Send feedback to email@example.com.
You can reach the Developer Platform team at firstname.lastname@example.org.
The Splunk Java Software Development Kit is licensed under the Apache License 2.0. Details can be found in the LICENSE file.