Splunk® Data Stream Processor

Release Notes

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.

Fixed Issues for DSP

This release includes fixes for the following issues.

Date resolved Issue number Description
2022-07-29 DSPOP-4211 The Write Thru KV Store function configuration cannot be updated through the Edit Streams JSON option in the pipeline metadata.
2022-07-28 DSPOP-5493 Upgrade from 1.2.x to 1.3.0 fails if DSP was installed with a custom state directory (--location or --state-dir)
2022-07-15 DSPOP-4210 When editing an active pipeline, toggling between builders reverts the pipeline definition to the last activated version.
2022-06-09 DSPOP-5566 HEC Async client stops processing data when error occurs
2022-06-09 DSPOP-5588 ./set-config (and other Bash scripts) fail when passing in values with whitespace characters (multiple single-word arguments separated by whitespace are fine). ./set-config can also fail when values start with dashes.
Last modified on 29 July, 2022
Known issues for DSP   Deprecated and removed features

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

Acrobat logo Download manual
Acrobat logo Download this page

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