Splunk® Data Stream Processor

Install and administer the Data Stream Processor

DSP 1.2.1 is impacted by the CVE-2021-44228 and CVE-2021-45046 security vulnerabilities from Apache Log4j. To fix these vulnerabilities, you must upgrade to DSP 1.2.4. See Upgrade the Splunk Data Stream Processor to 1.2.4 for upgrade instructions.

On October 30, 2022, all 1.2.x versions of the Splunk Data Stream Processor will reach its end of support date. See the Splunk Software Support Policy for details.
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.

Installation checklist for DSP

To inquire about the Splunk Data Stream Processor (DSP), contact your Splunk Sales representative.

Use the following checklist to install DSP with assistance from Splunk support.

Number Task Description Documentation
1 Review the known issues. Review the known issues reported in this DSP release. Known issues for DSP
2 Verify the requirements. Verify the DSP hardware and software requirements. Hardware and Software Requirements
3 Review the network encryption policies. Review where DSP does and does not provide network encryption. Network Encryption Policy
4 Configure the required ports. Configure the ports used for communication between Gravity and DSP. Port configuration requirements
5 Perform any additional prerequisite configuration and setup. Review the additional installation prerequisites and perform the steps as needed depending on your system configuration. Additional installation considerations
6 Run the DSP installer. Download the DSP tarball, extract the files and run the installer. Install the Data Stream Processor
7 (Optional) Secure the DSP cluster. By default, DSP uses self-signed certificates. You can configure your own SSL/TLS certificates for DSP Secure the DSP cluster with SSL/TLS certificates
8 (Optional) Configure server certificate validation. Configure the server certificate and hostname validation if your Splunk HEC endpoints are secured via HTTPS (SSL/TLS). Configure the Data Stream Processor to send data to a self-signed Splunk instance
9 Change the administrator password. Change the DSP administrator password. Change the admin password
10 Add a license. Add a DSP license. Licensing for the Splunk Data Stream Processor
11 Set up user accounts and verify permissions. Set up user accounts and verify associated permissions, roles, and capabilities. Manage users and admins
12 Configure the SCloud tool. SCloud is a command-line tool used to make API calls in DSP. SCloud is automatically installed for you during the installation process. Get Started with SCloud
13 (Optional) Configure the DSP cluster. You can change the default configuration of the DSP clusters as needed depending on your system configuration. Cluster configuration options
14 (Optional) Set up external services for data ingestion. DSP supports data from supported third-parties, REST APIs, or Splunk Forwarders. Admins can assist users of their tenant by setting up connections or Forwarders for use in their data pipelines. Getting started with Splunk DSP data connections
15 (Optional) Set up the data retention policies All data received by Splunk DSP Firehose is stored in a Pulsar topic for 24 hours. The oldest data in the topic is deleted first. You can adjust the data retention policy as needed depending on your requirements. Data retention policies
16 Test your DSP deployment. Create a test pipeline to confirm that DSP is receiving and sending data successfully. You can use the Splunk Firehose to Splunk Index template to do this. Create a pipeline using a template
17 (Optional) Install and configure the Splunk App for DSP. Use the Splunk App for DSP to monitor the health of your data pipelines. About the Splunk App for DSP
Last modified on 02 December, 2020
  What's in the installer directory?

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.0, 1.2.1-patch02, 1.2.1, 1.2.2-patch02, 1.2.4, 1.2.5, 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