<?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: Regex extraction in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Regex-extraction/m-p/75434#M19062</link>
    <description>&lt;P&gt;Looks like a typo in your props.conf? The section in transforms.conf is called &lt;CODE&gt;with_colon&lt;/CODE&gt; but the transform you're referring to in props.conf is &lt;CODE&gt;snare_colon&lt;/CODE&gt;.&lt;/P&gt;</description>
    <pubDate>Wed, 14 Sep 2011 18:06:44 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2011-09-14T18:06:44Z</dc:date>
    <item>
      <title>Regex extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Regex-extraction/m-p/75433#M19061</link>
      <description>&lt;P&gt;I am attempting to extract key value pairs from a data stream with the following syntax.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Successful Logon:     User Name: user     Domain: domain     Logon ID: (0x0,0x1480338F)     Logon Process: etc     Workstation Name:      Logon GUID: {d660922a-0228-f3f5-0acd-2052d7e03d22}     Caller User Name: -     Caller Domain: -     Caller Logon ID: -     Caller Process ID: -     Transited Services: -     Source Network Address: ...     
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;My transforms.conf contains&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[with_colon] 
REGEX = \s\s\s(.*?):\s(.*?)\s\s 
FORMAT = $1::$2 
CLEAN_KEYS = 1 
MV_ADD = 1
REPEAT_MATCH = true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and my props.conf contains&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[my_type]
# Derived from windows_snare_syslog
MAX_TIMESTAMP_LOOKAHEAD = 32
TRANSFORMS = syslog-host
REPORT-syslog = syslog-extractions
REPORT-colon = snare_colon
SHOULD_LINEMERGE = False
TIME_FORMAT = %b %d %H:%M:%S
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The regular expression works perfectly in my test environment (Notepad++ with the latest regex engine) but not a single new field is extracted. What am I doing wrong? &lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2011 17:51:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Regex-extraction/m-p/75433#M19061</guid>
      <dc:creator>timbCFCA</dc:creator>
      <dc:date>2011-09-14T17:51:52Z</dc:date>
    </item>
    <item>
      <title>Re: Regex extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Regex-extraction/m-p/75434#M19062</link>
      <description>&lt;P&gt;Looks like a typo in your props.conf? The section in transforms.conf is called &lt;CODE&gt;with_colon&lt;/CODE&gt; but the transform you're referring to in props.conf is &lt;CODE&gt;snare_colon&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2011 18:06:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Regex-extraction/m-p/75434#M19062</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2011-09-14T18:06:44Z</dc:date>
    </item>
    <item>
      <title>Re: Regex extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Regex-extraction/m-p/75435#M19063</link>
      <description>&lt;P&gt;Ayn.. Thanks so much. That was exactly the problem. Over the course of the implementation I changed the name slightly and hadn't updated it here. I now have a few hundred more fields I don't have to enter by hand.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2011 18:09:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Regex-extraction/m-p/75435#M19063</guid>
      <dc:creator>timbCFCA</dc:creator>
      <dc:date>2011-09-14T18:09:54Z</dc:date>
    </item>
  </channel>
</rss>

