Create a DSP connection to a Splunk index

To send data from a data pipeline in the to a Splunk index, you must first create a connection using the Connector for the Splunk Platform. You can then use the connection in the Send to Splunk HTTP Event Collector or Send to a Splunk Index sink functions to send data from your DSP pipeline to your Splunk index.

Prerequisites

• A Splunk Enterprise or Splunk Cloud Platform 7.1.0+ environment, with HTTP Event Collector enabled and a valid HEC token.
• If you are using an SSL-enabled HEC token or sending data to Splunk Cloud Platform, then you must configure the DSP environment variables to support SSL. See Configure the Data Stream Processor to send data to a self-signed Splunk instance.

Steps

1. In DSP, select the Connections page.
2. On the Connections page, click Create Connection.
3. On the Sink tab, select Connector for the Splunk Platform and then click Next.
4. Complete the following fields:

   Field	Description
   Connection Name	A unique name for your connection.
   Description (Optional)	A description of your connection.
   Splunk HEC endpoint URLs	Your HEC endpoint URLs, separated by commas. Load balancing is performed if more than one endpoint is provided. The HEC endpoint URL format varies depending on whether you are sending data to Splunk Enterprise or Splunk Cloud Platform. If you are connecting to Splunk Enterprise, then the HEC URLs must be formatted as https://hostname:port, https://hostname:port. If you are connecting to a paid Splunk Cloud Platform, then the HEC URLs must be formatted as https://http-inputs-<host1>.splunkcloud.com:443, https://http-inputs-<host2>.splunkcloud.com:443. By default, the paid version of Splunk Cloud Platform uses port number 443 to listen for connections. If you are connecting to a trial version of Splunk Cloud Platform, then the HEC URLs must be formatted as https://inputs.<host>.splunkcloud.com:8088. By default, the trial version of Splunk Cloud Platform uses port number 8088 to listen for connections.
   Splunk HEC endpoint token	HEC token for the Splunk Enterprise or Splunk Cloud Platform instance.

   Any credentials that you upload are transmitted securely by HTTPS, encrypted, and securely stored in a secrets manager.

5. Click Save.

If you're editing a connection that's being used by an active pipeline, you must reactivate that pipeline after making your changes. When you reactivate a pipeline, you must select where you want to resume data ingestion. See Using activation checkpoints to activate your pipeline in the Use the Data Stream Processor manual for more information.

You can now use your connection to send data to an index in Splunk Enterprise or Splunk Cloud Platform using the HTTP Event Collector. For detailed instructions on how to send data to Splunk Enterprise or Splunk Cloud Platform, see Connecting Splunk indexes to your DSP pipeline.