On April 3, 2023, Splunk Data Stream Processor will reach 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.
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
Date resolved
|
Issue number
|
Description
|
2020-10-21 |
DSP-14507 |
Unable to launch pods due to "cannot allocate memory" caused by leaked cgroups
|
2020-05-05 |
DSP-7430 |
Events forwarded from DSP to the Splunk platform with timestamp of 0 are indexed with _time of Jan 1, 1970
|
2020-02-04 |
DSP-17242 |
lsdc GET connectors returns lsdc-query-error after installation
|
2019-12-16 |
DSP-8731 |
DSP does not yet support LZ4 compression in reads and writes to Kafka
|
2019-11-18 |
DSP-14603 |
New Installations of DSP v1.0.0 on multi node clusters create only one kafka replica and partition
|
2019-11-13 |
DSP-14677 |
Splunk Enterprise Sink does not provide a valid empty "event" entry in HEC event JSON when "body" field is empty in DSP record
|
2019-11-12 |
DSP-14679 |
Splunk Enterprise Sink changes numeric value in body to an array of numbers
|
2019-11-05 |
DSP-14645 |
The DSP UI changes certain floats to ints
|
2019-11-03 |
DSP-14767 |
K8S_PIPELINES_DATA_SPLUNKD_SSL_CERT_BASE64 cannot be altered by deployments
|
2019-10-18 |
DSP-14573 |
If one node is removed from the cluster, minio may become read-only causing pipeline checkpointing to fail
|
Feedback submitted, thanks!