Configure the Splunk HEC source plugin in Palo Alto Networks Telemetry Pipeline to ingest logs for processing and routing.
This information is for Palo Alto Networks Telemetry Pipeline, which is a standalone
product separate from Cortex XCOR.
The Splunk HEC source plugin
(name: splunk, alias: splunk_hec) lets you ingest log data from the Splunk
HTTP Event Collector into a telemetry pipeline.This is a
push-based
source plugin.
Supported telemetry types
The Splunk HEC source plugin for Palo Alto Networks Telemetry Pipeline supports these telemetry types:
Logs
Metrics
Traces
Configuration parameters
Use the parameters in this section to configure the Splunk HEC source plugin. The
Palo Alto Networks Telemetry Pipeline web interface uses the items in the Name column to
describe these parameters. Pipeline configuration files
use the items in the Key column as YAML keys.
General
Name
Key
Description
Default
Address to Listen On
listen
Required. The address to listen on.
0.0.0.0
Port
port
Required. The port for Palo Alto Networks Telemetry Pipeline to listen on.
9880
Tag Key
tag_key
Specifies the key name to overwrite a tag. If set, the value of that key overwrites the tag.
none
Buffer Max Size
buffer_max_size
Sets the maximum chunk size for buffered data. If a single record exceeds this size, the plugin drops that record.
4M
Buffer Chunk Size
buffer_chunk_size
Required. Sets the default chunk size for buffered data. If a single record exceeds this size, the plugin temporarily increases the chunk size up to the value of buffer_max_size to accommodate it.
512K
Splunk Token
splunk_token
Your Splunk token for HTTP HEC.
none
Security and TLS
Name
Key
Description
Default
TLS
tls
If true, enables TLS/SSL. If false, disables TLS/SSL. Accepted values: true, false.
false
TLS Certificate Validation
tls.verify
If on, and if tls is true, enables TLS/SSL certificate validation. If off, disables TLS/SSL certificate validation. Accepted values: on, off.
Sets a limit for how much buffered data the plugin can write to memory, which affects backpressure. This value must follow Fluent Bit’s rules for unit sizes. If unspecified, no limit is enforced. For v2 pipelines, this parameter affects only pipelines with the Deployment or DaemonSet workload type. To learn more, see the v2 backpressure guide. For v3 pipelines, this parameter is independent from the OpenTelemetry memory_limiter and batch processors.
none
Assistant
Responses are generated using AI and may contain mistakes.