inputlookup
Description
Use the inputlookup
command to search the contents of a lookup table. The lookup table can be a CSV lookup or a KV store lookup.
Syntax
The required syntax is in bold.
- | inputlookup
- [append=<bool>]
- [strict=<bool>]
- [start=<int>]
- [max=<int>]
- <filename> | <tablename>
- [WHERE <search-query>]
Required arguments
You must specify either a <filename> or a <tablename>.
- <filename>
- Syntax: <string>
- Description: The name of the lookup file must end with
.csv
or.csv.gz
. If the lookup does not exist, a warning message is displayed (but no syntax error is generated).
- <tablename>
- Syntax: <string>
- Description: The name of the lookup table as specified by a stanza name in the
transforms.conf
file. The lookup table can be configured for any lookup type (CSV, external, or KV store).
Optional arguments
- append
- Syntax: append=<bool>
- Description: If set to
true
, the data returned from the lookup file is appended to the current set of results rather than replacing it. Defaults tofalse
.
- strict
- Syntax: strict=<bool>
- Description: When set to
true
this argument forces the search to fail completely ifinputlookup
raises an error. This happens even when the errors apply to a subsearch. When set tofalse
, manyinputlookup
error conditions return warning messages but do not otherwise cause the search to fail. Certain error conditions cause the search to fail even whenstrict=false
. - Default: false
- max
- Syntax max=<int>
- Description: Specify the maximum number of events to be read from the file. Defaults to
1000000000
.
- start
- Syntax: start=<int>
- Description: Specify the 0-based offset of the first event to read. If
start=0
, it begins with the first event. Ifstart=4
, it begins with the fifth event. Defaults to 0.
- WHERE clause
- Syntax: WHERE <search-query>
- Description: Use this clause to improve search performance by prefiltering data returned from the lookup table. Supports a limited set of search query operators: =, !=, <, >, <=, >=, AND, OR, NOT. Any combination of these operators is permitted. Also supports wildcard string searches.
Usage
The inputlookup
command is an event-generating command. See Command types.
Generating commands use a leading pipe character and should be the first command in a search.
The inputlookup
command can be first command in a search or in a subsearch.
The lookup can be a file name that ends with .csv
or .csv.gz
, or a lookup table definition in Settings > Lookups > Lookup definitions.
Appending or replacing results
When using the inputlookup
command in a subsearch, if append=true
, data from the lookup file or KV store collection is appended to the search results from the main search. When append=false
the main search results are replaced with the results from the lookup search.
Working with large CSV lookup tables
The WHERE clause allows you to narrow the scope of the query that inputlookup
makes against the lookup table. It restricts inputlookup
to a smaller number of lookup table rows, which can improve search efficiency when you are working with significantly large lookup tables.
Testing geometric lookup files
You can use the inputlookup
command to verify that the geometric features on the map are correct. The syntax is | inputlookup <your_lookup>
.
- For example, to verify that the geometric features in built-in geo_us_states lookup appear correctly on the choropleth map, run the following search:
| inputlookup geo_us_states
- On the Visualizations tab, zoom in to see the geometric features. In this example, the states in the United States.
Strict error handling
Use the strict
argument to make inputlookup
searches fail whenever they encounter an error condition. You can set this at the system level for all inputcsv
and inputlookup
searches by changing input_errors_fatal
in limits.conf
.
If you use Splunk Cloud Platform, file a Support ticket to change the input_errors_fatal
setting.
Use the strict
argument to override the input_errors_fatal
setting for an inputlookup
search.
Additional information
For more information about creating lookups, see About lookups in the Knowledge Manager Manual.
For more information about the App Key Value store, see About KV store in the Admin Manual.
Examples
1. Read in a lookup table
Read in a usertogroup
lookup table that is defined in the transforms.conf
file.
| inputlookup usertogroup
2. Append lookup table fields to the current search results
Using a subsearch, read in the usertogroup
lookup table that is defined by a stanza in the transforms.conf
file. Append the fields to the results in the main search.
... [| inputlookup append=t usertogroup]
3. Read in a lookup table in a CSV file
Search the users.csv
lookup file, which is in the $SPLUNK_HOME/etc/system/lookups
or $SPLUNK_HOME/etc/apps/<app_name>/lookups
directory.
| inputlookup users.csv
4. Read in a lookup table from a KV store collection
Search the contents of the KV store collection kvstorecoll
that have a CustID
value greater than 500 and a CustName
value that begins with the letter P. The collection is referenced in a lookup table called kvstorecoll_lookup
. Provide a count of the events received from the table.
| inputlookup kvstorecoll_lookup where (CustID>500) AND (CustName="P*")
| stats count
In this example, the lookup definition explicitly defines the CustID
field as a type of "number". If the field type is not explicitly defined, the where clause does not work. Defining field types is optional.
5. View the internal key ID values for the KV store collection
Example 5: View internal key ID values for the KV store collection kvstorecoll
, using the lookup table kvstorecoll_lookup
. The internal key ID is a unique identifier for each record in the collection. This example uses the eval
and table
commands.
| inputlookup kvstorecoll_lookup
| eval CustKey = _key
| table CustKey, CustName, CustStreet, CustCity, CustState, CustZip
6. Update field values for a single KV store collection record
Update field values for a single KV store collection record. This example uses the inputlookup
, outputlookup
, and eval
commands. The record is indicated by the its internal key ID (the _key
field) and this search updates the record with a new customer name and customer city. The record belongs to the KV store collection kvstorecoll
, which is accessed through the lookup table kvstorecoll_lookup
.
| inputlookup kvstorecoll_lookup
| search _key=544948df3ec32d7a4c1d9755
| eval CustName="Claudia Garcia"
| eval CustCity="San Francisco"
| outputlookup kvstorecoll_lookup append=true key_field=_key
7. Write the contents of a CSV file to a KV store collection
Write the contents of a CSV file to the KV store collection kvstorecoll
using the lookup table kvstorecoll_lookup
. The CSV file is in the $SPLUNK_HOME/etc/system/lookups
or $SPLUNK_HOME/etc/apps/<app_name>/lookups
directory.
| inputlookup customers.csv
| outputlookup kvstorecoll_lookup
See also
- Commands
- inputcsv
- join
- lookup
- outputlookup
inputintelligence | iplocation |
This documentation applies to the following versions of Splunk® Enterprise: 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.3.0, 9.3.1
Feedback submitted, thanks!