Splunk® Enterprise

Knowledge Manager Manual

Download manual as PDF

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

Add a lookup attribute

You can add a lookup attribute to any object in your data model.

In order to create a lookup attribute, you must have at least one lookup definition defined in Settings > Lookups > Lookup definitions. The lookup definition specifies the location of the lookup table and how to access it, either by reading an uploaded CSV file or by using a Python script to connect to an external lookup table. Once the lookup definition is in place, Splunk software can match the values of the attribute you choose to values of a field in the lookup table and then return corresponding field/value combinations and apply them to your object as lookup attributes.

Note: Any lookup table files and lookup definitions that you use in your lookup attribute must have the same permissions as the data model. If the data model's permissions are global (i.e., shared to "all apps"), but the lookup table file or definition is private, the attribute will be broken. (In general data models and their associated lookup table files and definitions should all be shared globally to all apps.)

For more information about creating lookup definitions (as well as uploading CSV files), see "Use field lookups to add information to your events".

6.1 dm add lookup att.png

1. In the Data Model Editor, open the object you'd like to add a lookup attribute to.

2. Click Add Attribute and select Lookup.

This takes you to the Add Attributes with a Lookup page.

3. Under Lookup Table, select the lookup table that you intend to match an input attribute to.

All of the values in the Lookup Table list are lookup definitions that were previously defined in Settings.
When you select a valid lookup table, the Input and Output sections of the page are revealed and populated. The Output section should display a list of all of the columns in the selected Lookup Table.

4. Under Input, define your lookup input fields. Choose a Field in Lookup (a field from the Lookup Table that you've chosen) and a corresponding Attribute from the object you're editing.

The Input lookup table field/attribute combination is the key that selects rows in the lookup table. For each row that this input key selects, you can bring in output field values from that row and add them to matching events.
For example, your object may have a productId field in your lookup table that matches an auto-extracted Product ID attribute in your object event data. The lookup table field and the object attribute should have the same (or very similar) value sets. In other words, if you have a row in your lookup table where productId has a value of PD3Z002, there should be events in your object dataset where theProduct ID = PD3Z002. Those matching events will be updated with output field/value combinations from the row where productId has a value of PD3Z002. See "Example of a lookup attribute setup," below, for a detailed step-by-step explanation of this process.
In cases where multiple lookup table rows are matched by a particular input key, field values from the first matching row are returned. To narrow down the set of rows that are matched, you can optionally define multiple pairs of input fields. For a row to be selected, all of these input keys must match. You cannot reuse Field in Lookup values when you have multiple inputs.

5. Under Output, determine which fields from the lookup will be added to eligible events in your object dataset as new lookup attributes.

You should find a list of fields here, pulled from the columns in the lookup table that you've chosen. Start by selecting the fields that you would like to add to your events. Any lookup fields that you've designated as inputs will be unavailable. You must define at least one output attribute in order for the lookup attribute definition to be valid.
If you do not find any fields here there may be a problem with the designated Lookup Table.

6. Under Field Name, provide the field name that the lookup attribute should have in your data.

Field Name values cannot include whitespace, single quotes, double quotes, curly braces, or asterisks.

7. Under Display Name provide the display name for the lookup attribute in the Data Model Editor and in Pivot.

Display Name values cannot include asterisk characters.

8. Set appropriate Type and Flags values for each lookup attribute that you define.

For more information about the Type field, see the subsection "Marking attributes as hidden or required" in the "Define object attributes" topic, in this manual.

9. (Optional) Click Preview to verify that the output attributes are being added to qualifying events.

Qualifying events are events whose input attribute values match up with input field values in the lookup table). See "Preview lookup attributes," below, for more information.

10. If you're satisfied that the lookup is working as expected, click Save to save your attributes and return to the Data Model Builder.

The new lookup attributes will be added to the bottom of the object attribute list.

Preview lookup attributes

After you set up your lookup attribute, you can click Preview to see whether the lookup attributes are being added to qualifying events (events where the designated input attribute values match up with corresponding input field values in the lookup table). Splunk Web displays the results in two or more tabbed pages.

The first tab shows a sample of the events returned by the underlying search. New lookup attributes should appear to the right of the first column (the _time column). If you do not see any values in the lookup attribute columns in the first few pages it could indicate that these values are very rare. You can check on this by looking at the remaining preview tab(s).

6.1 dm add lookup att values preview2.png

Splunk Web displays a tab for each lookup attribute you select in the Output section. Each attribute tab provides a quick summary of the value distribution in the chosen sample of events. It's set up as a top values list, organized by Count and percentage.

6.1 dm add lookup att values preview.png

Example of a lookup attribute setup

Let's say the following things are true:

  • You have a data model object with an auto-extracted attribute called Product ID and another auto-extracted attribute named Product Name. You would like to use a lookup table to add a new attribute to your dataset that provides the product price.
  • You have a .csv file called product_lookup. This table includes several fields related to products, including productId and product_name (which have very similar value sets to the similarly-named attributes in your object), as well as price, which is the field in the lookup table that you want to add to your object as a lookup attribute.
  • You know that there are a few products that have the same Product Name but different Product ID values and prices. This means you can't set up a lookup definition that depends solely on Product Name as the input field, because it will try to apply the same price value from the lookup table to two or more products. You'll have to design a lookup attribute definition that uses both Product Nameand Product ID as input fields, matching each combination of values in your matching events to rows in the lookup table that have the same name/ID combinations.

If this is the case, here's what you do to get price properly added to your object data as an attribute.

1. In Settings, create a lookup definition that points at the product_lookup.csv lookup file. Call this lookup definition product_lookup.

2. Go to Pivot and open the Data Model Editor for the object you want to add the lookup attributes to.

3. Click Add Attribute and select Lookup.

The Edit Attributes with a Lookup page opens.

4. Under Lookup Table select product_lookup.

All of the fields tracked in the lookup table will appear under Output.

5. Under Input, define two Field in Lookup/Attribute pairs. The first pair should have a Field in Lookup value of ProductId and an Attribute value of Product ID. The second pair should have a Field in Lookup value of product_name and an Attribute value of Product Name.

The first pair matches the lookup table's productId field with your object's Product ID attribute. The second pair matches the lookup table's product_name field with your object's Product Name attribute. Notice that when you do this, under Output the rows for the productID and product_name fields become unavailable.

6. Under Output, select the checkbox for the price field.

This setting specifies that you want to add it to the events in your object dataset that have matching input attributes.

7. Give the price attribute a Display Name of Price.

The price attribute should already have a Type value of Number.

8. Click Preview to test whether price is being added to your events.

The preview events appear in table format, and the price field is the second column after the timestamp.

9. If the price field shows up as expected in the preview results, click Save to save the lookup attribute.

Now your Pivot users will be able to use Price as an attribute option when building Pivot reports and dashboards.

PREVIOUS
Add an eval expression attribute
  NEXT
Add a regular expression attribute

This documentation applies to the following versions of Splunk® Enterprise: 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, 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.3.14, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11


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