Before you download and install the Splunk software, read this topic carefully to learn about which computing environments Splunk supports.
For a discussion of hardware planning for deployment, review "Hardware capacity planning for your Splunk Enterprise deployment" in this manual.
Supported server hardware architectures
Splunk offers support for 32 and 64-bit architectures on some platforms. See the download page for details.
Important: Read the following tables carefully when researching the system requirements. Splunk availability has changed significantly from previous versions.
The tables below list the computing platforms that Splunk is available for. The first table lists availability for *nix operating systems and the second lists availability for Windows operating systems.
To find out whether or not Splunk Enterprise is available for your platform:
1. Find the operating system you wish to install Splunk Enterprise on in the left column.
2. Then, read across to find the appropriate computing architecture in the center column that best matches your environment.
The tables show availability for two different types of Splunk, as shown in the two columns on the right: Splunk Enterprise/Trial, and Splunk Universal Forwarder. A '✔' in the box that intersects your computing platform and desired Splunk type means that Splunk is available for that platform. An empty box means that Splunk is not available for that platform.
Some boxes have characters instead of a '✔'. Refer to the bottom of the tables to find out what the additional characters represent.
Unix operating systems
|Operating system||Architecture||Enterprise / Trial||Universal Forwarder|
|Solaris 8||x86 (64-bit)||✔|
|Solaris 9||x86 (64-bit)||✔|
|Solaris 10 and 11*||x86 (64-bit)||✔||✔|
|Linux, 2.4+ with Native POSIX Thread Library||x86 (64-bit)|
|Linux, 2.6+||x86 (64-bit)||✔||✔|
|Linux, 3.0+||x86 (64-bit)||✔||✔|
|FreeBSD 7** and 8||x86 (64-bit)||✔||✔|
|FreeBSD 9||x86 (64-bit)||✔||✔|
|Mac OS X 10.7, 10.8, and 10.9||Intel||✔||✔|
|AIX 6.1 and 7.1||PowerPC||✔||✔|
|HP/UX† 11i v2 and 11i v3||Itanium||✔||✔|
* Splunk is available and supported on Solaris 10. Solaris 11 does not support 32-bit Splunk installs.
** Read important notes on FreeBSD 7 compatibility below.
† You must use gnu
tar to unpack the HP/UX installation archive.
Windows operating systems
The table below lists the Windows computing platforms that Splunk is available for.
|Operating system||Architecture||Enterprise / Trial||Universal Forwarder|
|Windows Server 2003 and Server 2003 R2||x86 (64-bit)||✔||✔|
|Windows Server 2008 and Server 2008 R2©||x86 (64-bit)||✔||✔|
|Windows Server 2012 and Server 2012 R2||x86 (64-bit)||✔||✔|
|Windows XP||x86 (64-bit)||✔|
|Windows Vista||x86 (64-bit)||¶||✔|
|Windows 7||x86 (64-bit)||✔||✔|
|Windows 8||x86 (64-bit)||✔||✔|
|Windows 8.1||x86 (64-bit)||¶||✔|
© There is no 32-bit version of Windows Server 2008 R2.
*** This version of Splunk is available and supported but is not recommended on this platform and architecture.
¶ Splunk Enterprise is not available on this platform. However, Splunk Trial and Splunk Universal Forwarder are available.
Operating system notes and additional information
Certain parts of Splunk on Windows require elevated user permissions to function properly. For additional information about what is required, read the following topics:
- "Splunk architecture and processes" in this manual.
- "Choose the user Splunk should run as" in this manual.
- "Considerations for deciding how to monitor remote Windows data" in the Getting Data In manual.
To run Splunk 6.x on 32-bit FreeBSD 7.x, install the
compat6x libraries. Splunk Support will supply "best effort" support for users running on FreeBSD 7.x.
For more information, refer to "Install Splunk on FreeBSD 7" in the Community Wiki.
Deprecated operating systems and features
As we continue to version the Splunk product, we gradually deprecate support of older operating systems. Read "Deprecated features" in the Release Notes for information on which platforms and features have been deprecated or removed entirely.
Creating and editing configuration files on non-UTF-8 OSes
Splunk expects configuration files to be in ASCII or Universal Character Set Transformation Format-8-bit (UTF-8) format. If you edit or create a configuration file on an OS that does not use UTF-8 character set encoding, then you must ensure that the editor you are using is configured to save in ASCII/UTF-8.
IPv6 platform support
All Splunk-supported OS platforms are supported for use with IPv6 configurations except for the following:
- HP/UX on PA-RISC architecture
- Solaris 9
Refer to "Configure Splunk for IPv6" in the Admin Manual for details on Splunk IPv6 support.
Splunk Enterprise supports the following browsers:
- Firefox ESR (24.2) and latest
- Internet Explorer 9, 10, and 11
- Safari (latest)
- Chrome (latest)
You should also make sure you have the latest version of Adobe Flash installed to render any charts that use options not supported by the JSChart module. For more information about this subject, read "About JSChart" in the Splunk Data Visualizations Manual.
Splunk Enterprise is a high-performance application. If you are performing a comprehensive evaluation of Splunk for production deployment, we recommend that you use hardware typical of your production environment. This hardware should meet or exceed the recommended hardware capacity specifications below.
For a discussion of hardware planning for production deployment, see "Hardware capacity planning for your Splunk deployment" in this manual.
Splunk and virtual machines
If you run Splunk Enterprise in a virtual machine (VM) on any platform, performance degrades. This is because virtualization works by abstracting the hardware on a system into resource pools from which VMs defined on the system draw as needed. Splunk Enterprise needs sustained access to a number of resources, particularly disk I/O, for indexing operations. Running Splunk in a VM or alongside other VMs can cause reduced indexing and search performance.
Recommended and minimum hardware capacity
|Platform||Recommended hardware capacity/configuration||Minimum supported hardware capacity|
|Non-Windows platforms||2x six-core, 2+ GHz CPU, 12 GB RAM, Redundant Array of Independent Disks (RAID) 0 or 1+0, with a 64 bit OS installed.||1x1.4 GHz CPU, 1 GB RAM|
|Windows platforms||2x six-core, 2+ GHz CPU, 12 GB RAM, RAID 0 or 1+0, with a 64 bit OS installed.||Intel Nehalem CPU or equivalent at 2 GHz, 2 GB RAM|
Note: RAID 0 configurations do not provide fault-tolerance. Be certain that a RAID 0 configuration meets your data reliability needs before deploying a Splunk indexer on a system configured with RAID 0.
- All configurations other than universal and light forwarder instances require at least the recommended hardware configuration.
- The minimum supported hardware guidelines are designed for personal use of Splunk. The requirements for Splunk in a production environment are significantly higher.
Important: For all installations, including forwarders, you must have a minimum of 5 GB of hard disk space available in addition to the space required for any indexes. Refer to "Estimate your storage requirements" in this manual for additional information.
Hardware requirements for universal and light forwarders
|Recommended||Dual-core 1.5 GHz+ processor, 1 GB+ RAM|
|Minimum||1.0 Ghz processor, 512 MB RAM|
Supported file systems
|Linux||ext2/3/4, reiser3, XFS, NFS 3/4|
|Solaris||UFS, ZFS, VXFS, NFS 3/4|
|FreeBSD||FFS, UFS, NFS 3/4, ZFS|
|Mac OS X||HFS, NFS 3/4|
|AIX||JFS, JFS2, NFS 3/4|
|HP-UX||VXFS, NFS 3/4|
Note: If you run Splunk Enterprise on a filesystem that is not listed above, Splunk might run a startup utility named
locktest to test the viability of a filesystem for running Splunk.
Locktest is a program that tests the start up process. If
locktest runs and fails, then the filesystem is not suitable for running Splunk.
Considerations regarding Network File System (NFS)
When you use Network File System (NFS) as a storage medium for Splunk indexing, consider all of the ramifications of file level storage.
Use block level storage rather than file level storage for indexing your data.
In environments with reliable, high-bandwidth, low-latency links, or with vendors that provide high-availability, clustered network storage, NFS can be an appropriate choice. However, customers who choose this strategy should work with their hardware vendor to confirm that the storage platform they choose operates to the specification in terms of both performance and data integrity.
If you use NFS, be aware of the following issues:
- Do not use NFS to host hot or warm index buckets as a failure in NFS can cause data loss. NFS works best with cold or frozen buckets.
- Do not use NFS to share cold or frozen index buckets amongst an indexer cluster, as this potentially creates a single point of failure.
- Do not use NFS mounts over a wide area network (WAN). Doing so causes performance issues and can lead to data loss.
- Splunk Enterprise does not support "soft" NFS mounts. These are mounts that cause a program attempting a file operation on the mount to report an error and continue in case of a failure.
- Only "hard" NFS mounts (mounts where the client continues to attempt to contact the server in case of a failure) are reliable with Splunk Enterprise.
- Do not disable attribute caching. If you have other applications that require disabling or reducing attribute caching, then you must provide Splunk Enterprise with a separate mount with attribute caching enabled.
Considerations regarding file descriptor limits (FDs) on *nix systems
Splunk Enterprise allocates file descriptors on *nix systems for actively monitored files, forwarder connections, deployment clients, users running searches, and so on.
Usually, the default file descriptor limit (controlled by the
ulimit -n command on a *nix-based OS) is 1024. Your Splunk administrator should determine the correct level, but it should be at least 8192. Even if Splunk allocates just a single file descriptor for each of the activities above, it’s easy to see how a few hundred files being monitored, a few hundred forwarders sending data, a handful of very active users on top of reading/writing to/from the datastore can easily exhaust the default setting.
The more tasks your Splunk Enterprise instance is doing, the more FDs it will need, so you should increase the ulimit value if you start to see your instance run into problems with low FD limits.
For more information, read about ulimit in the Troubleshooting Manual.
This consideration is not applicable to Windows-based systems.
Considerations regarding solid state drives
Solid state drives (SSDs) deliver significant performance gains over conventional hard drives for Splunk in "rare" searches - searches that request small sets of results over large swaths of data - when used in combination with bloom filters. They also deliver performance gains with concurrent searches overall.
Considerations regarding Common Internet File System (CIFS)/Server Message Block (SMB)
Splunk Enterprise supports the use of the CIFS/SMB protocol for the following purposes, on shares supported by Windows hosts only:
When you use a CIFS resource for storage, confirm that the resource has write permissions for the user that connects to the resource at both the file and share levels. If you use a third-party storage device, ensure that its implementation of CIFS is compatible with the implementation that your Splunk Enterprise instance runs as a client.
Do not attempt to index data to a mapped network drive on Windows (for example "
Y:\" mapped to an external share.) Splunk Enterprise disables any index it encounters with a non-physical drive letter.
Considerations regarding environments that use the transparent huge pages memory management scheme
If you run a Unix environment that makes use of transparent huge memory pages, see "Transparent huge memory pages and Splunk performance" before attempting to install Splunk Enterprise.
No such scheme exists on Windows operating systems.
Components of a Splunk Enterprise deployment