Splunk Enterprise and anti-virus products
Splunk Enterprise requires ample disk I/O bandwidth to perform indexing tasks. In particular, disk write operations are very intensive. These disk writes can clash with any product, such as anti-virus on-access scan software, that installs a driver that intermediates between Splunk Enterprise and the operating system.
When you run Splunk (Enterprise or forwarder) on a host that has an anti-virus product (such as McAfee VirusScan on Windows or Trend Micro ServerProtect on Linux) installed, Splunk strongly recommends that you exclude all Splunk processes as well as the Splunk installation directory from any kind of on-access scanning.
On Windows hosts, on-access scanners can significantly decrease performance. On *nix hosts, these scanners can use up file descriptors and render a host completely inaccessible.
Files and processes to exclude
The following table lists the Splunk platform directories and executables to exclude from anti-virus scanning.
|Version:||Directories to exclude:||Processes to exclude:|
|Splunk Enterprise (Windows)||
|Splunk universal forwarder (Windows)||
|Splunk Enterprise (*nix)||
|Splunk universal forwarder (*nix)||
||Same as Splunk Enterprise (*nix)|
Other items to exclude
If you run a Splunk app or add-on on your Splunk Enterprise instance or forwarder, exclude any executables that might come with the app or add-on. An example is the Splunk Add-on for PowerShell - this modular input comes with an executable named
powershell.exe that should also be excluded from anti-virus scans when it runs.
In general, any file associated with Splunk Enterprise that can be executed should be excluded from scanning. You might need to inspect additional files in apps or add-ons to determine whether or not they qualify.
Workaround for network accessibility issues on Splunk Windows systems under certain conditions
This documentation applies to the following versions of Splunk® Enterprise: 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4