Is my data local or remote?
When initially getting data into Splunk Enterprise, you might encounter some confusion as to what type of data is considered "local" and what type of data is considered "remote." The distinction between local and remote is particularly important when you are navigating the new data input pages.
The answer to this question depends on a number of criteria, including (but not limited to):
- The operating system on which your Splunk Enterprise instance resides
- The types of data stores that are directly connected to your Splunk Enterprise instance
- Whether any authentication or other intermediate steps are needed to access the data store that contains the data you want to index
A local resource is a fixed resource that your Splunk Enterprise server has direct access to, meaning you are able to access it - and whatever is contained within it - without having to attach, connect, or perform any other intermediate action (such as authentication or mapping a network drive) in order to have that resource appear available to your system. If your data is on such a resource, the data is considered "local."
Some examples of local data include:
- A hard disk or solid state drive installed in a desktop or laptop
- A RAM disk loaded at system start-up
A remote resource is any resource where the above definition is not satisfied. Network drives mapped from Windows systems, Active Directory schemas, and NFS or other network-based mounts on *nix systems are examples that qualify for this designation. Data gathered from these resource endpoints is also considered "remote."
There are cases where resources that would normally be considered remote are actually not. Here are some examples:
- A machine has a volume permanently mounted over a high-bandwidth physical connection such as USB or FireWire. Since the computer can mount the resource at boot time, it's treated as a local resource, even though the resource can theoretically be disconnected at a later time.
- A machine has a resource permanently mounted over a high-bandwidth network standard such as iSCSI, or to a Storage Area Network over fiber. As the standard treats such volumes as local block devices, such a resource would be considered local.
What Splunk Enterprise can index
Use forwarders to get data in
This documentation applies to the following versions of Splunk® Enterprise: 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, 6.0.13, 6.0.14, 6.0.15, 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, 6.1.13, 6.1.14, 6.2.0, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.2.12, 6.2.13, 6.2.14, 6.2.15