Connecting Microsoft Azure Event Hubs to your DSP pipeline as a data destination (Beta)
If you have a Universal license for Splunk Data Stream Processor, you can connect to Microsoft Azure Event Hubs and use it as a data destination. You can get data into a data pipeline, transform it, and then send the transformed data to event hub. See Licensing for the Splunk Data Stream Processor in the Install and administer the Data Stream Processor manual for information about licensing.
The Send to Microsoft Azure Event Hubs sink function, which is used for sending data from DSP to Azure Event Hubs, is a beta function and not ready for production.
To connect to Azure Event Hubs as a data destination, you must complete the following tasks:
- If the event hub that you want to send data to does not already exist in your Azure Event Hubs namespace, create it. For information about creating an event hub, search for "Quickstart: Create an event hub using Azure portal" in the Azure Event Hubs documentation.
If you try to send data to an event hub that does not already exist, the pipeline fails to send data to Azure Event Hubs and returns an error.
- Create a connection that allows DSP to send data to your event hub. See Create a DSP connection to Microsoft Azure Event Hubs.
- Create a pipeline that ends with the Send to Microsoft Azure Event Hubs 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 Microsoft Azure Event Hubs sink function to use your Azure Event Hubs connection and send data to an existing event hub. See Send data to Microsoft Azure Event Hubs (Beta) in the Function Reference manual.
When you activate the pipeline, the sink function starts sending data from the pipeline to the specified event hub.
Connecting Microsoft Azure Event Hubs to your DSP pipeline as a data source
Create a DSP connection to Microsoft Azure Event Hubs
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
Feedback submitted, thanks!