Connecting Kafka to your DSP pipeline as a data source
When creating a data pipeline in Splunk Data Stream Processor (DSP), you can connect to an Apache Kafka or Confluent Kafka broker and use it as a data source. You can get data from Kafka into a pipeline, transform the data as needed, and then send the transformed data out from the pipeline to a destination of your choosing.
If you have a Universal license, you can also use Kafka as a data destination. See Connecting Kafka to your DSP pipeline as a data destination for information about this use case. See Licensing for the Splunk Data Stream Processor for information about licensing.
DSP supports two types of connections for accessing Kafka brokers:
- SSL-authenticated connections, which are suitable for use in production environments. This type of connection uses two-way SSL authentication, where the client and server authenticate each other using the SSL/TLS protocol.
- Unauthenticated connections, which should only be used for testing purposes in a secure internal environment.
To connect to Kafka as a data source, you must complete the following tasks:
- Create a connection that allows DSP to access your Kafka data.
- To create an SSL-authenticated connection, see Create an SSL-authenticated DSP connection to Kafka.
- To create an unauthenticated connection, see Create an unauthenticated DSP connection to Kafka.
- Create a pipeline that starts with the Kafka source function. See the Building a pipeline chapter in the Use the manual for instructions on how to build a data pipeline.
- Configure the Kafka source function to use your Kafka connection. See Get data from Kafka in the Function Reference manual.
- (Optional) Convert the byte-encoded data from Kafka records into strings that are human-readable during data preview and usable in streaming functions that require string input. See Deserialize and preview data from Kafka in DSP.
When you activate the pipeline, the source function starts collecting data from Kafka. The data is received into the pipeline as a records that contain byte-encoded data values.
If your data fails to get into DSP, check the connection settings to make sure you have the correct broker, as well as the correct certificates and keys if you are using an SSL-authenticated connection. DSP doesn't run a check to see if you enter valid credentials.
Create a DSP connection to get metadata from AWS
Connecting Kafka to your DSP pipeline as a data destination
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.0, 1.2.1