Splunk® Data Stream Processor

Install and administer the Data Stream Processor

On April 3, 2023, Splunk Data Stream Processor reached its end of sale, and will reach its end of life on February 28, 2025. If you are an existing DSP customer, please reach out to your account team for more information.

All DSP releases prior to DSP 1.4.0 use Gravity, a Kubernetes orchestrator, which has been announced end-of-life. We have replaced Gravity with an alternative component in DSP 1.4.0. Therefore, we will no longer provide support for versions of DSP prior to DSP 1.4.0 after July 1, 2023. We advise all of our customers to upgrade to DSP 1.4.0 in order to continue to receive full product support from Splunk.
This documentation does not apply to the most recent version of Splunk® Data Stream Processor. For documentation on the most recent version, go to the latest release.

What's in the installer directory?

The following table describes the files that you'll see in the installer tarball for the Splunk Data Stream Processor (DSP).

Item in the directory Description
README A README text file containing information about the Splunk Software License Agreement and links to the DSP documentation.
configure-ui A script used to configure the UI redirect URL.
dsp-version A text file containing your DSP version.
eula.txt A text file containing information about the Splunk Software License Agreement.
examples A directory containing Buttercup Games sample data for use.
get-config Returns the configuration of a specified property.
get-secret Returns the value associated with a specified secret key.
gravity A directory containing metadata about the Gravity environment.
install The script that begins the DSP install process.
join A script used to join a node to your cluster.
leave A script used to remove a node from your cluster.
list-configs Returns a list of configurations that you've set. Does not include default configurations.
list-secrets Returns a list of secrets that you've set.
pre-upgrade A script that assists in manually upgrading your DSP deployment. Don't use this script unless Splunk Support instructs you to do so.
post-upgrade A script that assists in manually upgrading your DSP deployment. Don't use this script unless Splunk Support instructs you to do so.
print-login Returns the DSP UI login information.
print-services Returns a list of DSP services, including the IP and port information for each service.
remove-config Removes a specified configuration.
remove-secret Removes a specified secret.
report Generates a report containing information about the health of your deployment.
reset-admin-password A script used to change the default admin password to a user-specified one.
rolling-reactivate A script that reactivates all currently active pipelines.
scloud.v1 Version 1 of the Splunk CLI tool used to make API calls to these DSP services: Ingest, Forwarders, Identity, and Streams. See Get started with SCloud.
scloud.v4 Version 4 of the Splunk CLI tool used to make API calls to these DSP services: Ingest, Forwarders, Collect, Identity, and Streams. This is the default version. See Get started with SCloud.
set-config A script used to set configuration properties for DSP.
set-secret A script used to set a secret for DSP.
splunk_app_dsp-1.0.3.tar.gz The tarball containing the Splunk App for DSP.
upgrade A script used to upgrade an existing version of DSP.
wait-for-active A script used as part of the install script. When invoked, the install script waits until the cluster reaches active status before continuing.
wait-for-running A script used as part of the upgrade script. When invoked, the upgrade script waits until all services are running before continuing.
Last modified on 25 March, 2022
Installation checklist for DSP   Hardware and Software Requirements

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.3.0, 1.3.1


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters