--- title: "Splunk configuration" slug: "splunk-configuration" tags: ["Reference", "Helix", "Sec Ops and Analytics"] updated: 2026-09-02T19:14:18Z published: 2026-09-02T19:14:18Z canonical: "docs.trellix.com/splunk-configuration" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Splunk configuration There are three types of Splunk Fowarders: Universal, Heavy, and Light. The only forwarder that supports SYSLOG is a Heavy Forwarder. The following links provide data on forwarding data from Splunk: - [http://docs.splunk.com/Documentation/Splunk/5.0.4/Deploy/Deployaforwarder](http://docs.splunk.com/Documentation/Splunk/5.0.4/Deploy/Deployaforwarder) - [http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Forwarddatatothird- partysystemsd#Forward_syslog_data](http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Forwarddatatothird-partysystemsd#Forward_syslog_data) Validate that logs were being forwarded to the Comm Broker Sender by running this `tcpdump` command: ``` tcpdump port 514 host -A ``` The Splunk GUI may flash a message saying that forwarding has stopped due to a spike in event volume. The message also may say there is a lack of open files or memory. In the event Splunk stops forwarding data and starts dropping events, do the following: 1. Modify the memory setting on the Splunk server in one of the following locations: - `/etc/security/limits.conf` - `/etc/security/limits.d/90-nproc.conf` (Red Hat) 2. Add these parameters to the file: - `soft nproc 10240` - `hard nproc 10240` - `soft nofile 65536` - `hard nofile 65536` 3. Reboot the server. 4. Clear all the stale queries. 5. Add the following to the splunk `output.conf` file: `sendCookedData = false` > [!NOTE] > Note > > After each step, restart Splunk. 6. Clear all the stale queries. 7. Add the following to the splunk `output.conf` file: `sendCookedData = false` > [!NOTE] > Note > > After each step, restart Splunk.