Before you download and install the Splunk software, read the following sections for the supported system requirements. If you have ideas or requests for new features to add to future releases, email Splunk Support. Also, you can follow our Product Roadmap.
Refer to the download page for the latest version to download. Check the release notes for details on known and resolved issues.
For a discussion of hardware planning for deployment, check out the topic on capacity planning in this manual.
Splunk is supported on the following platforms.
To run Splunk 4.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 this Community wiki topic.
Splunk expects configuration files to be in ASCII/UTF-8. If you are editing or creating a configuration file on an OS that is non-UTF-8, you must ensure that the editor you are using is configured to save in ASCII/UTF-8.
Splunk 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, check out the topic on capacity planning in this manual.
Note: Running Splunk in virtual machine (VM) mode on any platform will degrade performance.
| Platform | Recommended hardware capacity/configuration | Minimum supported hardware capacity |
|---|---|---|
| Non-Windows platforms | 2x quad-core Xeon, 3GHz, 8GB RAM, RAID 0 or 1+0, with a 64 bit OS installed. | 1x1.4 GHz CPU, 1 GB RAM |
| Windows platforms | 2x quad-core Xeon, 3GHz, 8GB RAM, RAID 0 or 1+0, with a 64 bit OS installed. | Pentium 4 or equivalent at 2Ghz, 2GB RAM |
Important: For all installations including forwarders, a minimum of 2GB hard disk space for your Splunk installation is required in addition to the space required for your index. Refer to this topic on estimating your index size requirements in this manual for some planning information.
| Recommended | Dual Core 1.5Ghz+ processor, 1GB+ RAM |
| Minimum | 1.0 Ghz processor, 512MB RAM |
| Platform | File systems |
|---|---|
| Linux | ext2/3, reiser3, XFS, NFS 3/4 |
| Solaris | UFS, ZFS, VXFS, NFS 3/4 |
| FreeBSD | FFS, UFS, NFS 3/4 |
| Mac OS X | HFS, NFS 3/4 |
| AIX | JFS, JFS2, NFS 3/4 |
| HP-UX | VXFS, NFS 3/4 |
| Windows | NTFS, FAT32 |
NFS is usually a poor choice for Splunk indexing activity, for reasons of performance, resilience, and semantics. In environments with very high bandwidth, very low latency links, that are kept highly reliable, it can be an appropriate choice. Typically, this is a NAS accessed via the NFS protocol.
Note: Several other file systems are supported. If you run Splunk on a filesystem that is not listed above, Splunk may run a startup utility named locktest. Locktest is a program that tests the start up process. If locktest runs and fails, the filesystem is not suitable for running Splunk.
Note: On FreeBSD, mounting as nullfs is not supported.
32 and 64-bit architectures are supported for some platforms. See the download page page for details.
In the below comment, i wrote wrong version of splunk, it is splunk 4.1.3(80534)and my server is having 1gb ram and 3.19ghz (windows server 2003, 32 bit)
Hello,
We are trying to use splunk in our company, I installed trial version splunk 4.2 on the integration server (windows server 2003, 32 bit machine), it installed successfully but when i run splunk, it would open login page, and when i enter username:admin Password:changeme, It would just keep loading forever, We really wanted to get splunk running as quickly as possible to be able to investigate out Production log files. Please help me. My email address is garlapati.mrudula@jobcorps.org
Rachel Said...
as requested above, please ask questions about difficulties with Splunk on http://answers.splunk.com. The documentation comment threads are for questions and discussion about the documentation.