<?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: Extract fields from an already extracted field in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215710#M63239</link>
    <description>&lt;P&gt;Aaaargggg - all the "backslashes" have been removed &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; &lt;/P&gt;</description>
    <pubDate>Fri, 30 Oct 2015 16:31:02 GMT</pubDate>
    <dc:creator>markwymer</dc:creator>
    <dc:date>2015-10-30T16:31:02Z</dc:date>
    <item>
      <title>Extract fields from an already extracted field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215707#M63236</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;I'm trying to extract the &lt;CODE&gt;filename&lt;/CODE&gt; and &lt;CODE&gt;file ext&lt;/CODE&gt; of a windows path into to different fields. The &lt;CODE&gt;sourcetype&lt;/CODE&gt; is &lt;CODE&gt;CSV&lt;/CODE&gt; and the &lt;CODE&gt;path&lt;/CODE&gt; is already extracted into a field called &lt;CODE&gt;Threat Target File Path&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;The event looks like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;10/30/15 8:01:40 AM,Z4437-E6A5-58E3,10.221.7.210,C:\Users\u106420\Videos\WP_20140610_002.mp4,NT AUTHORITY\SYSTEM,C:\Windows\system32\svchost.exe
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The field &lt;CODE&gt;Threat Target File Path&lt;/CODE&gt; contains:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;C:\Users\u106420\Videos\WP_20140610_002.mp4
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And I would like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Threat Target File Name = WP_20140610_002
Threat Target File Ext = mp4
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I would like 'automate' this so I'm guessing that i need to add entries into the &lt;CODE&gt;transforms.conf&lt;/CODE&gt; and &lt;CODE&gt;props.conf&lt;/CODE&gt;,&lt;/P&gt;

&lt;P&gt;Is this possible and what entries would I need to get the two additional field extractions?&lt;/P&gt;

&lt;P&gt;Many thanks for any help,&lt;BR /&gt;
Mark.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Oct 2015 12:24:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215707#M63236</guid>
      <dc:creator>markwymer</dc:creator>
      <dc:date>2015-10-30T12:24:26Z</dc:date>
    </item>
    <item>
      <title>Re: Extract fields from an already extracted field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215708#M63237</link>
      <description>&lt;P&gt;sorry just noticed a typo. The '\' have been removed from the Path name. It should be &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;10/30/15 8:01:40 AM,Z4437-E6A5-58E3,10.221.7.210,C:\Users\u112200\Videos\WP_20140610_002.mp4,NT AUTHORITY\SYSTEM,C:\Windows\system32\svchost.exe&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;and the "Threat Target File Path" is&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;C:\Users\u112200\Videos\WP_20140610_002.mp4&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;Hopefully, this will now look better&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 07:47:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215708#M63237</guid>
      <dc:creator>markwymer</dc:creator>
      <dc:date>2020-09-29T07:47:09Z</dc:date>
    </item>
    <item>
      <title>Re: Extract fields from an already extracted field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215709#M63238</link>
      <description>&lt;P&gt;Nope - all the '\'s get removed!&lt;/P&gt;</description>
      <pubDate>Fri, 30 Oct 2015 15:55:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215709#M63238</guid>
      <dc:creator>markwymer</dc:creator>
      <dc:date>2015-10-30T15:55:11Z</dc:date>
    </item>
    <item>
      <title>Re: Extract fields from an already extracted field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215710#M63239</link>
      <description>&lt;P&gt;Aaaargggg - all the "backslashes" have been removed &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 30 Oct 2015 16:31:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215710#M63239</guid>
      <dc:creator>markwymer</dc:creator>
      <dc:date>2015-10-30T16:31:02Z</dc:date>
    </item>
    <item>
      <title>Re: Extract fields from an already extracted field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215711#M63240</link>
      <description>&lt;P&gt;Try this:&lt;/P&gt;

&lt;P&gt;Inside &lt;CODE&gt;props.conf&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;REPORT-this_part_does_not_matter_but_must_come_below_whatever_created_Threat_Target_File_Path = filename_into_two_parts
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Inside &lt;CODE&gt;transforms.conf&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[filename_into_two_parts]
SOURCE_KEY="Threat Target File Path"
REGEX=[^\.]+?(?&amp;lt;ThreatTargetFileName&amp;gt;[^\\\.]+)(?:\.(?&amp;lt;ThreatTargetFileExt&amp;gt;[^\\\.]*))?$
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 30 Oct 2015 17:13:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215711#M63240</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-10-30T17:13:59Z</dc:date>
    </item>
    <item>
      <title>Re: Extract fields from an already extracted field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215712#M63241</link>
      <description>&lt;P&gt;Hi @markwymer&lt;/P&gt;

&lt;P&gt;Make sure to use the text editor tools in the "ask a question" UI to render special characters properly. @woodcock (thanks!) already edited your post for you, but in the future, whenever you're sharing sample code, data, search strings, conf file stanzas (especially anything with regex), etc., highlight it and click the &lt;STRONG&gt;Code Sample&lt;/STRONG&gt; button. This will wrap it in a code box so it appears as it should. If you're sharing a snippet of code or regex within a sentence, you can enclose it between two back-ticks (&lt;CODE&gt;) so it appears like this&lt;/CODE&gt;!@#$%^&amp;amp;*&lt;EM&gt;%^$\*|&lt;/EM&gt;\`&lt;/P&gt;</description>
      <pubDate>Fri, 30 Oct 2015 23:06:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Extract-fields-from-an-already-extracted-field/m-p/215712#M63241</guid>
      <dc:creator>ppablo</dc:creator>
      <dc:date>2015-10-30T23:06:30Z</dc:date>
    </item>
  </channel>
</rss>

