Splunk® Data Stream Processor

Release Notes

Acrobat logo Download manual as PDF


This documentation does not apply to the most recent version of DSP. Click here for the latest version.
Acrobat logo Download topic as PDF

Known issues for DSP

This version of the Splunk Data Stream Processor has the following known issues and workarounds.

If no issues appear here, no issues have yet been reported.

Highlighted issues

Date filed Issue number Description
2020-10-21 DSP-28545 After upgrading from DSP 1.1 to 1.2, scheduled Collect service jobs fail due to an ImagePullBackoff error.

Workaround:
Manually apply a specific service account to the service that triggers Collect service jobs. Work with Professional Services to get this service account spec.
2020-09-18 DSP-26954 Activated pipelines cannot be reactivated after upgrading.

Workaround:
Reactivate your pipelines with "Skip Restore State" enabled. Since "Skip Restore State" discards the saved state of your pipeline, your pipeline ignores any data ingested while it is deactivated causing data loss.

Uncategorized issues

Date filed Issue number Description
2021-12-03 DSP-43606 Server can be attacked by slow clients during TLS handshake
2021-09-02 DSP-41953 DSP's messaging bus does not write to a write-ahead log by default. In some cases, this may cause data loss.
2021-08-04 DSP-41040 Checkpoint cleanup for pull-based connectors cause performance issues.
2021-06-21 DSP-39621 Network policies can prevent legitimate internal service communication

Workaround:
Rarely, internal network policies can be incorrectly generated leading to disruption of internal cluster communications. Symptoms include persistent Connection Reset and Connection Timeout messages between services that should normally be allowed to communicate.

To remediate: kubectl delete netpol -A --all

If affected by this issue, internal service communication should be restored almost immediately. Note that network policy objects will be restored after running ./deploy. The above command should be re-applied after ./deploy.

2021-06-07 DSP-38856 Send to Splunk Sink Functions: Pipelines using the "Send to Splunk…" sink functions have frequent restarts due to "HEC async client" errors.
2021-06-01 DSP-38591 Subseconds are not sent to Firehose
2020-10-19 DSP-28423 The connection_id dropdown does not work for pipelines migrated from 1.1 that use the splunk_enterprise_indexes or splunk_enterprise sink functions.

Workaround:
1. Deactivate the pipeline

2. Click on the Ellipsis (More Options menu) next to "Activate Pipeline" and expand the Streams JSON Import/Export menu.

3. Update the resolvedId of the affected functions.

For splunk_enterprise_indexes, update the value of "resolvedId" to "into_splunk_enterprise_indexes:collection<record<R>>:connection-id:expression<string>:expression<string>"

For splunk_enterprise, update the value of "resolvedId" to "into_splunk_enterprise:collection<record<R>>:connection-id:expression<string>:expression<bytes>"

4. Save the updated metadata.

5. Save and reactivate the pipeline.

2020-10-07 DSP-27878 Apply Line Break function metrics show twice the number of records.
2020-09-30 DSP-27483 On macOS, you cannot accept the warning for the self-signed TLS certificate

Workaround:
Type "thisisunsafe" in the browser window to accept the certificate.
2020-09-18 DSP-26912 Generated SPL can erroneously duplicate statement names when statement names of the form statement_n are hard-coded in the Pipeline JSON.

Workaround:
Change the hard-coded statement names in the Pipeline JSON to something that does not match statement_n.
2020-09-10 DSP-26551 DSP installation pre-flight check for disk space should check the correct volume/directory.

Workaround:
/var/data is always erroneously checked for disk size, even if another volume is specified with --location. You can symlink where you intend to install to /var/data as a workaround.

For example, if you use --location /data, first ln -s /data /var/data

2020-08-31 DSP-26064 Upgrading DSP gives a "HTTPS Status 500 - Internal Server Error" on initial login.

Workaround:
Clear your browser cache and then try logging back into DSP.
2020-04-30 DSP-20769 Migration prompt continues to show up after an active pipeline is migrated to a new API version.
2020-04-21 DSP-20380 When toggling between the Canvas Builder and SPL2 Builder, function configurations are unexpectedly populated with default values.

Workaround:
Configure every function so the UPL is valid.
2020-04-08 DSP-19759 DSP does not properly ingest sourcetypes with INDEXED_EXTRACTIONS=true.
Last modified on 09 May, 2022
PREVIOUS
New features for DSP
  NEXT
Fixed Issues for DSP

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.2-patch02


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