Getting Data In

Find more things to monitor with crawl

This feature has been deprecated.
This feature has been deprecated as of Splunk Enterprise version 6.0. This means that although it continues to function, it might be removed in a future version. As an alternative, you can search for files and directories to monitor manually. For a list of all deprecated features, see the topic "Deprecated features" in the Release Notes.

Use the crawl search command to search your file system or network for new data sources to add to your Splunk Enterprise index.

You can change default crawler settings by editing crawl.conf. You can override the crawler defaults at the time that you run crawl.

crawl produces a log of crawl activity which it stores in $SPLUNK_HOME/var/log/splunk/crawl.log.

Change crawler defaults

Edit $SPLUNK_HOME/etc/system/local/crawl.conf to change the default crawler configuration settings. You define the files and network crawlers separately, in their own stanzas.

Syntax

crawl.conf contains two stanzas: [files] and [network], which define defaults for the files and network crawlers, respectively.

For information on the definable attributes for those stanzas and their default values, read the crawl.conf spec file.

Example

Here's an example crawl.conf file with settings defined for both the files and network crawlers:

[files]
bad_directories_list= bin, sbin, boot, mnt, proc, tmp, temp, home, mail, .thumbnails, cache, old
bad_extensions_list= mp3, mpg, jpeg, jpg,  m4, mcp, mid
bad_file_matches_list= *example*, *makefile, core.*
packed_extensions_list= gz, tgz, tar, zip
collapse_threshold= 10
days_sizek_pairs_list= 3-0,7-1000, 30-10000
big_dir_filecount= 100
index=main
max_badfiles_per_dir=100

[network]
host = myserver
subnet = 24