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.
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.
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
Feedback submitted, thanks!