Knowledge Manager Manual


Configure multivalue fields

Configure multivalue fields

Multivalue fields are fields that can appear multiple times in an event and have a different value for each appearance. One of the more common examples of multivalue fields is that of email address fields, which typically appears two to three times in a single sendmail event--once for the sender, another time for the list of recipients, and possibly a third time for the list of Cc addresses, if one exists. If all of these fields are labeled identically (as "AddressList," for example), they lose meaning that they might otherwise have if they're identified separately as "From", "To", and "Cc".

Splunk Enterprise parses multivalue fields at search time, and enables you to process the values in the search pipeline. Search commands that work with multivalue fields include makemv, mvcombine, mvexpand, and nomv. For more information on these and other commands see the topic on multivalue fields in the User manual, and the Search Reference manual.

Use the TOKENIZER key to configure multivalue fields in fields.conf. TOKENIZER uses a regular expression to tell Splunk Enterprise how to recognize and extract multiple field values for a recurring field in an event. Edit fields.conf in $SPLUNK_HOME/etc/system/local/, or your own custom app directory in $SPLUNK_HOME/etc/apps/.

For more information on configuration files in general, see "About configuration files" in the Admin manual.

For a primer on regular expression syntax and usage, see You can test regexes by using them in searches with the rex search command. Splunk Enterprise also maintains a list of useful third-party tools for writing and testing regular expressions.

Configure a multivalue field via fields.conf

Define a multivalue field by adding a stanza for it in fields.conf. Then add a line with the TOKENIZER key and a corresponding regular expression that shows how the field can have multiple values.

Note: If you have other attributes to set for a multivalue field, set them in the same stanza underneath the TOKENIZER line. See the fields.conf topic in the Admin manual for more information.

[<field name 1>]
TOKENIZER = <regular expression>

[<field name 2>]
TOKENIZER = <regular expression>
  • <regular expression> should indicate how the field in question can take on multiple values.
  • TOKENIZER defaults to empty. When TOKENIZER is empty, the field can only take on a single value.
  • Otherwise the first group is taken from each match to form the set of field values.
  • The TOKENIZER key is used by the where, timeline, and stats commands. It also provides the summary and XML outputs of the asynchronous search API.

Note: Tokenization of indexed fields (fields extracted at index time) is not supported. If you have set INDEXED=true for a field, you cannot also use the TOKENIZER key for that field. You can use a search-time extraction defined in props.conf and transforms.conf to break an indexed field into multiple values.


Say you have a poorly formatted email log file where all of the addresses involved are grouped together under AddressList:

To:  ,,
CC:  ,,
Subject:       Multivalue fields are out there!
X-Mailer:      Febooti Automation Workshop (Unregistered)
Content-Type:  text/plain; charset=UTF-8
Date:          Wed, 3 Nov 2014 17:13:54 +0200
X-Priority:    3 (normal)

This example from $SPLUNK_HOME/etc/system/README/fields.conf.example breaks email fields To, From, and CC into multiple values.

TOKENIZER = (\w[\w\.\-]*@[\w\.\-]*\w)

TOKENIZER = (\w[\w\.\-]*@[\w\.\-]*\w)

TOKENIZER = (\w[\w\.\-]*@[\w\.\-]*\w)

This documentation applies to the following versions of Splunk: 5.0 , 5.0.1 , 5.0.2 , 5.0.3 , 5.0.4 , 5.0.5 , 5.0.6 , 5.0.7 , 5.0.8 , 5.0.9 , 5.0.10 , 5.0.11 , 5.0.12 , 5.0.13 , 5.0.14 , 6.0 , 6.0.1 , 6.0.2 , 6.0.3 , 6.0.4 , 6.0.5 , 6.0.6 , 6.0.7 , 6.0.8 , 6.0.9 , 6.0.10 , 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.2.0 , 6.2.1 , 6.2.2 , 6.2.3 , 6.2.4 , 6.2.5 View the Article History for its revisions.


I added an example event to better illustrate how you can use fields.conf to set up multivalued field extractions.<br /><br />However, as I researched this I realized that this sort of extraction is probably better configured in props.conf and transforms.conf using the MV_ADD parameter in transforms.conf. Here's an example that shows you how this parameter is used:<br /><br />It looks like MV_ADD can effectively replace the usage of fields.conf for most cases of multivalued field extraction. See this link for more examples of MV_ADD: <br /><br />I'll update the documentation around this after I do a bit more research.

August 25, 2014

Thanks for the document. <br /><br />Please post a sample log entry with the article. I will be really handy to understand what is the target text being processed. Not sure if this documents needs to be referred with any other complimentary resources.

August 22, 2014

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

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.

Feedback submitted, thanks!