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 before July 1, 2023 in order to continue to receive full product support from Splunk.
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.
|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 k0s 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||Review the DSP CLI tool.||The DSP CLI is a command-line tool used to configure and run DSP. The DSP CLI is included in the DSP installer package and does not require setup.||Get started with the Data Stream Processor CLI|
|14||(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|
|15||(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|
|16||(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|
|17||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|
|18||(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|
What's in the installer directory?
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.4.0, 1.4.1, 1.4.2, 1.4.3