Troubleshoot the input process
Not finding the events you're looking for?
When you add an input to Splunk Enterprise, that input gets added relative to the app you are in. Some apps, like the *nix and Windows apps, write input data to a specific index (in the case of *nix and Windows, that is the 'os' index). If you are not finding data that you are certain is in Splunk Enterprise, be sure that you are looking at the right index. You might want to add the 'os' index to the list of default indexes for the role you are using. For more information about roles, refer to the topic about roles in the Securing Splunk Enterprise manual. For more information about troubleshooting data input issues, read the rest of this topic or see "I can't find my data!" in the Troubleshooting Manual.
Note: When you add inputs by editing
inputs.conf, Splunk Enterprise might not immediately recognize them. Splunk Enterprise looks for inputs every 24 hours, starting from the time it was last restarted. This means that if you add a new stanza to monitor a directory or file, it could take up to 24 hours for Splunk Enterprise to start indexing the contents of that directory or file. To ensure that your input is immediately recognized and indexed, add the input through Splunk Web or by using the
add command in the CLI.
Troubleshoot your tailed files
You can use the
FileStatus Representational State Transfer (REST) endpoint to get the status of your tailed files. For example:
You can also monitor the fishbucket.
The fishbucket is a subdirectory within the Splunk platform directory that keeps a record about each file input. The fishbucket keeps track of how far into a file the Splunk platform has read, so that if you stop and restart splunkd, it knows where in each file input to resume reading. The fishbucket is at
To monitor the fishbucket, use the REST endpoint. Review the REST API Reference for additional information.
Troubleshoot monitor inputs
For a variety of information on dealing with monitor input issues, read Troubleshooting Monitor Inputs in the Community Wiki.
Can't find data coming from a forwarder?
Make sure the forwarder is functioning properly and is visible to the indexer. You can use the Deployment Monitor app to troubleshoot Splunk topologies and get to the root of any forwarder issues. Read the Deploy and Use Splunk Deployment Monitor App manual for details.
Use persistent queues to help prevent data loss
This documentation applies to the following versions of Splunk® Enterprise: 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