Splunk® Data Stream Processor

Connect to Data Sources and Destinations with DSP

Acrobat logo Download manual as PDF

DSP 1.2.0 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.
This documentation does not apply to the most recent version of DSP. Click here for the latest version.
Acrobat logo Download topic as PDF

Create a DSP connection to Microsoft Azure Event Hubs

To get data from Microsoft Azure Event Hubs into a data pipeline in the , or send data from a pipeline to an event hub, you must first create a connection. You can then use the connection in the Microsoft Azure Event Hubs source function or sink function.

Send to Microsoft Azure Event Hubs is a beta function and not ready for production.


Before you can create an Azure Event Hubs connection, you must have the following:

  • The shared access signature (SAS) key and name for accessing your Azure Event Hubs resources. If you don't have these credentials, ask your Azure Event Hubs administrator for assistance.
  • Outbound ports 5671 and 5672 open in the firewalls of all the nodes in the DSP cluster. If these outbound ports are not open, DSP cannot communicate with Azure Event Hubs. Ask your DSP administrator to confirm the port configurations and open the ports if needed.


  1. From the Data Stream Processor home page, click Data Management and then select the Connections tab.
  2. Click Create New Connection.
  3. Select Connector for Microsoft Azure Event Hubs and then click Next.
  4. Complete the following fields:
    Field Description
    Name A unique name for your Azure Event Hubs connection.
    Description (Optional) A description of your your Azure Event Hubs connection.
    Namespace name The name of the Azure Event Hubs namespace used to read and write events
    SAS name The name of the Shared Access Signature (SAS) key used to authenticate to Azure Event Hubs.
    SAS key The SAS key used to authenticate to Azure Event Hubs. Your shared access key must have listening privileges for the namespace.

    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 in a Microsoft Azure Event Hubs source function at the start of your data pipeline to get data from Azure Event Hubs, or in a Send to Microsoft Azure Event Hubs sink function at the end of your pipeline to send data to Azure Event Hubs.

Last modified on 26 February, 2022
Connecting Microsoft Azure Event Hubs to your DSP pipeline as a data destination (Beta)
Deserialize and preview data from Microsoft Azure Event Hubs in DSP

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

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