Splunk® Data Stream Processor

Release Notes

Acrobat logo Download manual as PDF


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.
Acrobat logo Download topic as PDF

Fixed Issues for DSP

This release includes fixes for the following issues.

Date resolved Issue number Description
2022-01-31 DSP-26551 DSP installation pre-flight check for disk space should check the correct volume/directory.
2021-12-08 DSP-43606 Server can be attacked by slow clients during TLS handshake
2021-10-08 DSP-39621 Network policies can prevent legitimate internal service communication
2021-06-24 DSP-38591 Subseconds are not sent to Firehose
2020-10-26 DSP-19759 DSP does not properly ingest sourcetypes with INDEXED_EXTRACTIONS=true.
2020-10-14 DSP-27878 Apply Line Break function metrics show twice the number of records.
2020-10-06 DSP-27483 On macOS, you cannot accept the warning for the self-signed TLS certificate
2020-09-30 DSP-26912 Generated SPL can erroneously duplicate statement names when statement names of the form statement_n are hard-coded in the Pipeline JSON.
Last modified on 18 March, 2022
PREVIOUS
Known issues for DSP 		  NEXT
Deprecated and removed features

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

Was this documentation topic helpful?


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