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.
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.
Change the admin password
Perform the following steps to change the dsp-admin password.
The dsp admin print-login command only returns the original password generated by the installer. If you forget your changed admin password, you'll need to reset your password again.
- From the working directory of a controller node, run the reset password script.
sudo dsp admin reset-password
- Enter your new password.
- Navigate back to the DSP UI and login with your new password.
Last modified on 13 January, 2023
| Configure the Data Stream Processor to send data to a self-signed Splunk instance | Set a default Splunk Enterprise instance for the Send to a Splunk Index (Default for Environment) function |
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6
Download manual
Feedback submitted, thanks!