Splunk® Data Stream Processor

Connect to Data Sources and Destinations with DSP

DSP 1.2.1 is impacted by the CVE-2021-44228 and CVE-2021-45046 security vulnerabilities from Apache Log4j. To fix these vulnerabilities, you must upgrade to DSP 1.2.4. See Upgrade the Splunk Data Stream Processor to 1.2.4 for upgrade instructions.

On October 30, 2022, all 1.2.x versions of the Splunk Data Stream Processor will reach its end of support date. See the Splunk Software Support Policy for details.

Connecting multiple data destinations to your DSP pipeline

When creating a data pipeline in the , you can choose to connect multiple data destinations to the pipeline. For example, you can create a single pipeline that sends data to a Splunk index, Amazon Kinesis Data Streams, and Amazon S3 concurrently. You can get data into the pipeline, transform the data, and then send the transformed data to all three data destinations.

To connect a pipeline to multiple data destinations, configure a connection and sink function for each data destination, and then branch the pipeline to end with each of these sink functions. See Send data to multiple destinations in a pipeline in the Use the Data Stream Processor manual for more information.

Last modified on 25 March, 2022
Connecting multiple data sources to your DSP pipeline   Connecting Amazon CloudWatch to your DSP pipeline

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.0, 1.2.1-patch02, 1.2.1, 1.2.2-patch02, 1.2.4, 1.2.5, 1.3.0, 1.3.1, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5


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