The Splunk Software Development Kit for Python (Beta Release)
This SDK 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.
The Splunk Software Development Kit for Python is licensed under the Apache License 2.0. Details can be found in the file LICENSE.
In order to use the SDK you are going to need a copy of Splunk. If you don't already have a copy you can download one from http://www.splunk.com/download.
You can get a copy of the SDK sources by cloning into the repository with git:
You can install the Splunk SDK libraries by using
[sudo] easy_install splunk-sdk
[sudo] pip install splunk-sdk
Alternatively, you can use
setup.py on the sources you cloned from GitHub:
[sudo] python setup.py install
However, it's not necessarry to install the libraries in order to run the examples and unit tests from the SDK.
The SDK requires Python 2.6+.
Running the examples and units
In order to run the Splunk examples and unit tests, you must put the root of the SDK on your PYTHONPATH.
The SDK command line examples require a common set of command line arguments
that specify things like the Splunk host and port and login credentials. You
can get a full list of command line arguments by typing
--help as an argument
to any of the command line examples.
The examples and units are also desigend to receive arguments from an optional
.splunkrc file located in your home directory. The format of the file is
simply a list of key=value pairs, same as the options that are taken on the
command line, for example:
host=localhost username=admin password=changeme
.splunkrc file is a feature of the SDK examples and unit tests and not
the Splunk platform or SDK libraries and is intended simply as convenience for
developers using the SDK.
.splunkrc file should not be used for storing user credentials for apps
built on Splunk and should not be used if you are concerned about the security
of the credentails used in your development environment.
You can view a sample
.splunkrc file by looking at the
in the root directory of the repistory.
The Splunk developer platform consists of three primary components:
splunkweb, the app framework that sits on top of the engine,
and the Splunk SDKs that interface with the REST API.
This SDK enables developers to target
splunkd by making calls against the
engine's REST API and by accessing the various
splunkd extension points such
as custom search commands, lookup functions, scripted inputs and custom REST
You can find additional information about building applications on Splunk at our developer portal at http://dev.splunk.com.
The Splunk library included in this SDK consists of two layers of API that can be used to interact with splunkd. The lower layer is referred to as the binding layer. It is a thin wrapper around low-level HTTP capabilities, including:
- A pluggable HTTP component that can be user-supplied.
- Handles authentication and namespace URL management
- Accessible low-level HTTP interface for use by developers who want to be close to the wire.
You can see an example use of the library here:
import splunklib.binding as binding # host defaults to localhost and port defaults to 8089 context = binding.connect(username="admin", password="changeme") response = context.get('/services/authentication/users') print "Status: %s" % response.status print response.body.read()
The second layer is referred to as the client layer and builds on the binding layer to provide a friendlier interface to Splunk that abstracts away some of the lower level details of the binding layer.
import splunklib.client as client # host defaults to localhost and port defaults to 8089 service = client.connect(username="admin", password="changeme") for user in service.users: print user.name
The SDK contains a small but growing collection of unit tests. Running the tests is simple and rewarding:
Alternatively, you can read more about our testing "framework" here.
Layout of the repository
|docs||Source for Sphinx based docs and build|
|examples||Examples demonstrating various SDK features|
|splunklib||Source for the Splunk library modules|
|tests||Source for unit tests|
|utils||Source for utilities shared by the examples and unit tests|
You can look at the changelog for each version here
master branch always represents a stable and released version of the SDK.
You can read more about our branching model on our
You can find anything having to do with developing on Splunk at the Splunk developer portal:
Reference documentation for the Python SDK:
Reference documentation for the Splunk REST API:
Overview of Splunk and links to additional product information:
Stay connected with other developers building on Splunk.
How to contribute
If you would like to contribute to the SDK, please follow one of the links provided below.
- You will be granted support if you or your company are already covered under an existing maintenance/support agreement. Send an email to email@example.com and please include the SDK you are referring to in the subject.
- If you are not covered under an existing maintenance/support agreement you can find help through the broader community at:
Splunk dev google group - http://groups.google.com/group/splunkdev
- Splunk will NOT provide support for SDKs if the core library (this is the code in the splunklib directory) has been modified. If you modify an SDK and want support, you can find help through the broader community and Splunk answers (see above). We also want to know about why you modified the core library. You can send feedback to: firstname.lastname@example.org
You can reach the Dev Platform team at email@example.com