<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why am I having issues with two fields that hold multi-values in one time import of OpenLDAP Data ? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-am-I-having-issues-with-two-fields-that-hold-multi-values-in/m-p/399488#M115819</link>
    <description>&lt;P&gt;MV_ADD is a transforms.conf directive, not props.    If you want to rerun a regular expression multiple times , you need to combine props and transforms.  &lt;/P&gt;

&lt;P&gt;I can't see your data, but I think something like the following would work: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;#add these lines to your props.conf
[LDAP Format]
disabled = 0
REPORT-01-parseGroupMembers = parsegroupmembers
REPORT-02-parseComments = parsecomments

#add these to transforms.conf
[parsegroupmembers]
disabled = 0
SOURCE_KEY = _raw
DEST_KEY = groupmembers
REGEX = groupmembers\=([^\r\n]+)
FORMAT = groupmembers::$1
MV_ADD = true

[parsecomments]
disabled = 0
SOURCE_KEY = _raw
DEST_KEY = comments
REGEX = comment\=([^\r\n]+)
FORMAT = comments::$1
MV_ADD = true
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 21 Jun 2018 17:18:26 GMT</pubDate>
    <dc:creator>darrenfuller</dc:creator>
    <dc:date>2018-06-21T17:18:26Z</dc:date>
    <item>
      <title>Why am I having issues with two fields that hold multi-values in one time import of OpenLDAP Data ?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-am-I-having-issues-with-two-fields-that-hold-multi-values-in/m-p/399487#M115818</link>
      <description>&lt;P&gt;I am importing a dump from my openLDAP into splunk via on one-time "data-import" .  The fields,  O, OU, DN, MAIL, etc are one value fields  and are no issue. I am having issues with two fields that hold multi-values.   One multivalue (comment) starts with a date value.&lt;/P&gt;

&lt;P&gt;ie:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;comment=20180604123700|admin-name|some admin comment string here
comment=20180604125700|admin-name|some admin comment string here
comment=20180612105700|admin-name|some admin comment string here
comment=20180616021500|admin-name|some admin comment string here
...
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The other mulitvalue is groupmembers:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;groupmembers=group_1
groupmembers=group_2
groupmembers=group_3
groupmembers=group_4
...
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;My problem with the comments appears that splunk sees the "date" and stops processing after that. It wont treat the entire line as a value string which is what I need.  &lt;/P&gt;

&lt;P&gt;My problem with "groupmembers" is that splunk only takes the first value and ignores the rest. I have tried setting MV_ADD to "true" on the "advanced settings" but it does not change how splunk handles it. The same is true for comments....all I get is the first "date" and nothing else.     &lt;/P&gt;

&lt;P&gt;My props.conf file from the import:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[LDAP Format]
BREAK_ONLY_BEFORE = dn=
MAX_TIMESTAMP_LOOKAHEAD = 4096
NO_BINARY_CHECK = true
TIME_PREFIX = approvaldate=
description = Ldap Import Sourcetype
disabled = false
pulldown_type = true
MV_ADD = true
MAX_DAYS_AGO = 5475
category = Application
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any advice would be greatly appreciated. Thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jun 2018 15:22:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-am-I-having-issues-with-two-fields-that-hold-multi-values-in/m-p/399487#M115818</guid>
      <dc:creator>johnjj7141</dc:creator>
      <dc:date>2018-06-21T15:22:04Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I having issues with two fields that hold multi-values in one time import of OpenLDAP Data ?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-am-I-having-issues-with-two-fields-that-hold-multi-values-in/m-p/399488#M115819</link>
      <description>&lt;P&gt;MV_ADD is a transforms.conf directive, not props.    If you want to rerun a regular expression multiple times , you need to combine props and transforms.  &lt;/P&gt;

&lt;P&gt;I can't see your data, but I think something like the following would work: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;#add these lines to your props.conf
[LDAP Format]
disabled = 0
REPORT-01-parseGroupMembers = parsegroupmembers
REPORT-02-parseComments = parsecomments

#add these to transforms.conf
[parsegroupmembers]
disabled = 0
SOURCE_KEY = _raw
DEST_KEY = groupmembers
REGEX = groupmembers\=([^\r\n]+)
FORMAT = groupmembers::$1
MV_ADD = true

[parsecomments]
disabled = 0
SOURCE_KEY = _raw
DEST_KEY = comments
REGEX = comment\=([^\r\n]+)
FORMAT = comments::$1
MV_ADD = true
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 21 Jun 2018 17:18:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-am-I-having-issues-with-two-fields-that-hold-multi-values-in/m-p/399488#M115819</guid>
      <dc:creator>darrenfuller</dc:creator>
      <dc:date>2018-06-21T17:18:26Z</dc:date>
    </item>
    <item>
      <title>Re: Why am I having issues with two fields that hold multi-values in one time import of OpenLDAP Data ?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-am-I-having-issues-with-two-fields-that-hold-multi-values-in/m-p/399489#M115820</link>
      <description>&lt;P&gt;Awesome....worked like a champ.... AND I now understand MV_ADD better!  Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jun 2018 18:17:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-am-I-having-issues-with-two-fields-that-hold-multi-values-in/m-p/399489#M115820</guid>
      <dc:creator>johnjj7141</dc:creator>
      <dc:date>2018-06-25T18:17:40Z</dc:date>
    </item>
  </channel>
</rss>

