Splunk is a SIEM solution for storing and processing logs. Tenzir can send data to Splunk via HEC.
Examples
Section titled “Examples”Send data to an existing HEC endpoint
Section titled “Send data to an existing HEC endpoint”To send data from a pipeline to a Splunk HTTP Event Collector (HEC)
endpoint, use the to_splunk operator.
For example, deploy the following pipeline to forward Suricata alerts to Splunk:
subscribe "suricata"where @name == "suricata.alert"to_splunk "https://1.2.3.4:8088", hec_token="TOKEN", tls_no_verify=trueReplace 1.2.3.4 with the IP address of your Splunk host and TOKEN with your
HEC token.
For more details, see the documentation for the
to_splunk operator.
Spawn a HEC endpoint as pipeline source
Section titled “Spawn a HEC endpoint as pipeline source”To send data to a Tenzir pipeline instead of Splunk, you can open a Splunk HTTP
Event Collector (HEC) endpoint using the
from_fluent_bit source operator.
For example, to onboard all data into a Tenzir node instead of Splunk, point your data source to the IP address of the Tenzir node at port 9880 by deploying this pipeline:
from_fluent_bit "splunk", options={ splunk_token: "TOKEN",}publish "splunk"Replace TOKEN with the Splunk token configured at your data source.
To listen on a different IP address, e.g., 1.2.3.4 add listen: 1.2.3.4 to the
options argument.
For more details, read the official Fluent Bit documentation of the Splunk input.