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 before July 1, 2023 in order to continue to receive full product support from Splunk.
Connecting Google Cloud Storage to your DSP pipeline as a data destination
When creating a data pipeline in the , you can connect to Google Cloud Storage and use it as a data destination. You can get data into a data pipeline, transform it, and then send the transformed data to a Cloud Storage bucket.
To connect to Google Cloud Storage as a data destination, you must complete the following tasks:
- If the bucket that you want to send data to does not already exist in your Google Cloud Storage instance, create it. For information about creating a Cloud Storage bucket, search for "Creating storage buckets" in the Google Cloud Storage documentation.
- Create a connection that allows DSP to send data to your Cloud Storage bucket. See Create a DSP connection to send data to Google Cloud Storage.
- Create a pipeline that ends with the Send to Google Cloud Storage sink function. See the Building a pipeline chapter in the Use the Data Stream Processor manual for instructions on how to build a data pipeline.
- Configure the Send to Google Cloud Storage sink function to use your Google Cloud Storage connection and send data to an existing Cloud Storage bucket. See Send data to Google Cloud Storage in the Function Reference manual.
When you activate the pipeline, the sink function starts sending data from the pipeline to the specified Cloud Storage bucket.
Deserialize and preview data from Google Cloud Pub/Sub in DSP
Create a DSP connection to send data to Google Cloud Storage
This documentation applies to the following versions of Splunk® Data Stream Processor: 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