Map Splunk Connect for Kafka settings to the Splunk Distribution of OpenTelemetry Collector for Kafka
Configuration mapping
You cannot transfer settings directly from Splunk Connect for Kafka to the Splunk Distribution of OpenTelemetry Collector for Kafka because the products use different architectures. However, many settings have equivalent options. Use the table below to map each setting.
In the Splunk Distribution of OpenTelemetry Collector for Kafka, configure settings on individual receivers (data sources) and exporters (data destinations). Then connect the components in a pipeline.
Settings supported by the Splunk Distribution of OpenTelemetry Collector for Kafka
|
Splunk Connect for Kafka field |
Splunk Distribution of OpenTelemetry Collector for Kafka setting |
Description |
|---|---|---|
|
|
|
Configure one topic per Kafka receiver. Add multiple receivers to a pipeline to collect from multiple topics. See Collector design. |
|
|
|
Prefix the topic pattern with |
|
|
|
Configure one |
|
|
|
Configure one |
|
|
|
Configure one |
|
|
|
Splunk HEC endpoint. |
|
|
|
Token for authenticating with Splunk HEC. |
|
|
|
Sends only the log body to a Splunk HEC raw endpoint. |
|
|
|
Specifies whether to skip certificate validation for the HEC endpoint over HTTPS. The default is |
|
|
|
Specifies whether to check Splunk HEC health when the exporter starts. |
|
|
|
Maximum number of simultaneous HTTP connections to Splunk HEC. The default is 100. |
|
|
|
Number of spans, metric data points, or log records to batch before sending. The default is 1000. |
|
|
|
Timeout for Splunk exporter operations. |
|
|
|
Socket timeout for Splunk exporter operations. |
|
|
|
When |
|
|
|
Extract custom headers and use them with custom processors. |
|
|
|
Maps Kafka header values to Splunk index metadata by using custom processors. |
|
|
|
Maps Kafka header values to Splunk source metadata by using custom processors. |
|
|
|
Maps Kafka header values to Splunk sourcetype metadata by using custom processors. |
|
|
|
Maps Kafka header values to Splunk host metadata by using custom processors. |
|
|
|
Configure timestamp extraction with processors. See Extract timestamps. |
|
|
|
Regular expression for extracting timestamps from log data. |
|
|
|
Format of extracted timestamps. |
|
|
|
Time zone for extracted timestamps. |
Settings without an equivalent in the Splunk Distribution of OpenTelemetry Collector for Kafka
|
Splunk Connect for Kafka field |
Description |
|---|---|
|
|
The Splunk Distribution of OpenTelemetry Collector for Kafka uses receivers, processors, and exporters instead of a connector class. |
|
|
Configure scaling differently. See Scale the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
Configure line breaking with custom processors. |
|
|
Configure JSON enrichment with custom processors. |
|
|
Configure timestamp extraction with processors. See Extract timestamps. |
|
|
Not supported by the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
Not supported by the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
Not supported by the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
Not supported by the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
Not supported by the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
Not supported by the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
Not supported by the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
Not supported by the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
Not supported by the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
The Splunk Distribution of OpenTelemetry Collector for Kafka does not use channels. |
|
|
Threading is managed differently and does not require explicit configuration. |
|
|
Handle data tracking and debugging with custom processors or external monitoring tools. |
|
|
Send events already formatted for HEC with the |
|
|
Trust store configuration is not supported by the Splunk Distribution of OpenTelemetry Collector for Kafka. |
|
|
|
|
|
Kerberos authentication is supported by the Kafka receiver. For details, see the Kafka receiver configuration. |
|
|