Splunk® Enterprise

User Manual

Download manual as PDF

Splunk version 4.x reached its End of Life on October 1, 2013. Please see the migration information.
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

Specify one or multiple indexes to search

You have always been able to create new indexes and manage where you want to store your data. Now, when you have data split across different indexes, you're no longer limited to searching one index at a time — you can search across multiple indexes at once!

The Splunk administrator can set the default indexes that a user searches. Based on the user's roles and permissions, he may have access to one or many indexes; for example the user may only be able to search main or all public indexes. The user can then specify a subset of these indexes, either an individual index or multiple indexes, to search. For more information about setting up users and roles, see the "About users and roles" chapter in the Admin manual.

For more information about managing your indexes and setting up multiple indexes, see the "About managing indexes" chapter in the Admin manual.

Control index access via Splunk Web

Navigate to 'Manager >> Access controls >> Roles'. Select the role that the User has been assigned to and then on the bottom of the next screen you'll find the index controls. You can control the indexes that particular role has access to, as well as the default search indexes.

Syntax

You can specify different indexes to search in the same way that you specify field names and values. In this case, the field name is index and the field value is the name of a particular index:

index=<indexname>

Note: When you type "index=" into the search bar, typeahead displays all the indexes that you can search, based on your roles and permissions settings.

Alternatively, you can specify indexes to exclude from your search using "index!=". When you specify indexes to exclude, all indexes are scanned to know which ones to exclude.

You can use the * wildcard to specify groups of indexes; for example, if you wanted to search both "mail" and "main" indexes, you can search for:

index=mai*

You can also use parentheses to partition different searches to certain indexes. See Example 3 for details.

Examples

Example 1: Search across all public indexes.

index=*

Example 2: Search across all indexes, public and internal.

index=* OR index=_*

Example 3: Partition different searches to different indexes; in this example, you're searching three different indexes: main, _internal, and mail. You want to see events that match "error" in all three indexes; but also, errors that match "warn" in main or "failed" in mail.

(index=main (error OR warn)) OR (index=_internal error) OR (index=mail (error OR failed))

Example 4: Search across multiple indexes on different distributed Splunk servers.

(splunk_server=local index=main 404 ip=10.0.0.0/16) OR (splunk_server=remote index=mail user=admin)

Not finding the events you're looking for?

When you add an input to Splunk, that input gets added relative to the app you're in. Some apps write input data to their own specific index (for example, the Splunk App for Unix and Linux uses the 'os' index).

If you're not finding data that you're certain is in Splunk, be sure that you're looking at the right index. You might need to add an app-specific index to the list of default indexes for the role you're using. For more information about roles, refer to the topic about roles in this manual.

PREVIOUS
Search and report in real time
  NEXT
Search across one or more distributed search peers

This documentation applies to the following versions of Splunk® Enterprise: 4.3, 4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7


Comments

Apologies, that should not have been a link. Corrected now, thanks for pointing it out.

Cgales splunk, Splunker
August 21, 2012

I like how clicking the "looking at the right index" link brings you right back to this same page

Msharp smcm
August 16, 2012

Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters