The new docs.trellix.com features a modernized UI and AI-powered conversational search. Content is currently available in English, with additional languages launching in early November 2026. We hope you enjoy the updated experience.

Splunk configuration

Prev Next

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:

Validate that logs were being forwarded to the Comm Broker Sender by running this tcpdump command:

tcpdump port 514 host <IP address of Splunk Server/Fowarder> -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

    After each step, restart Splunk.

  6. Clear all the stale queries.

  7. Add the following to the splunk output.conf file:

    sendCookedData = false

    Note

    After each step, restart Splunk.