Splunk Gen 2
The Splunk connector enables Belden Horizon Data Operations (BHDO) to publish data to Splunk via the HTTP Event Collector (HEC).
Supported communication
- Outbound (Publish data from Edge to Splunk) - Yes
- Inbound (Subscribe data from Splunk to Edge) - No
Configurations
Field | Details | Required |
|---|---|---|
Name | Name of the connector instance. | Yes |
Hostname | Splunk server host name. | Yes |
Port | Port of the Splunk HEC host. | Yes |
Use SSL | Use an HTTPS connection to the Splunk HEC endpoint. | Yes |
Endpoint | Splunk HEC endpoint path. | Yes |
Token | HEC token for access to the Splunk server. | Yes |
Throttling limit | Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost. | No |
Persistent storage configurations
Field | Details | Required |
|---|---|---|
Persistent storage | If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages are retained and eventually sent when the connection is restored. | No |
Persistent storage size limit | Set the size limit for storing persisted data in GB. | No |
Queue mode | Select the sequence of data transfer: FIFO or LIFO. Selecting FIFO (First In First Out) sends the earliest message first. Selecting LIFO (Last In First Out) sends the latest message first. | No |