About getting data into Splunk Enterprise
Before you can use Splunk Enterprise, you need to add data to it. When the data source is defined, Splunk Enterprise begins to index the data stream and transform it into a series of individual events that you can view and search. If the results are not what you want, tweak the indexing process until you are satisfied.
This topic is a brief overview of the types of data that you can add to Splunk, the ways to get that data into Splunk, and where Splunk stores that data after you add it.
What kinds of data?
Splunk Enterprise works with any data. In particular, all IT streaming and historical data. This data is from event logs, web logs, live application logs, network feeds, system metrics, change monitoring, message queues, archive files, and so on.
The data can be on the same machine as the Splunk indexer (local data), or it can be on another machine (remote data). For information on local versus remote data, see "Where is my data?" in the Getting Data In manual.
In general, categorize input sources as follows:
- Files and directories: A lot of data you might be interested in comes directly from files and directories.
- Network events: Splunk can index remote data from any network port and SNMP events from remote devices.
- Window sources: The Windows version of Splunk includes a wide range of Windows-specific inputs, including Windows Event Log, Windows Registry, WMI, Active Directory, and Performance monitoring.
- Other sources: Splunk also supports other input sources, such as FIFO queues and scripted inputs for getting data from APIs and other remote data interfaces.
For information about data and Splunk Enterprise, see "What Splunk can index" in the Getting Data In manual.
How to specify data inputs
You add new types of data to Splunk by defining the input sources. There are a number of ways to do this:
- Splunk Web. You can configure most inputs using the Splunk Web data input pages. These views provide a GUI-based approach to configuring inputs. Use this method to add the tutorial data into Splunk.
- Apps. Splunk has a large variety of apps and add-ons that offer preconfigured inputs for types of data sources. For more information, see "Use apps."
- Splunk's CLI. You can use the CLI (command line interface) to configure most types of inputs. See "Use the CLI."
- The inputs.conf configuration file. When you specify your inputs with Splunk Web or the CLI, the configurations are saved in an inputs.conf file. To handle some advanced data input requirements, you might need to edit that file directly. See "Edit inputs.conf" in the Getting Data In manual.
For more information on configuring inputs, see "Configure your inputs" in the Getting Data In manual.
Where Splunk stores data
A Splunk data repository is called an index. During indexing (or event processing), Splunk processes the incoming data stream to enable fast search and analysis, storing the results in the index as events.
Events are stored in the index as a group of files that fall into two categories:
- Rawdata, which is the raw data in a compressed form.
- Index files and some metadata files that point to the raw data.
Splunk, by default, puts all user data into a single, preconfigured index. It also uses several other indexes for internal purposes. You can add new indexes and manage existing ones to meet your data requirements. See "About managing indexes" in the Managing Indexers and Clusters manual.
Now that you're more familiar with Splunk data inputs and indexes, see "Get the tutorial data into Splunk Enterprise."
Navigating Splunk Web
Get the tutorial data into Splunk
This documentation applies to the following versions of Splunk® Enterprise: 6.1, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.1.12