<?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: Trouble extracting GUIDS and how to make a new field with rex? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621103#M215911</link>
    <description>&lt;P&gt;I hope you're not trying to validate the format of each GUID with regex because that is unnecessary.&amp;nbsp; Just extract everything after "fieldx':" as-is.&amp;nbsp; If you wish, you can split the extracted field on commas so each GUID is accessible using &lt;FONT face="courier new,courier"&gt;mvindex&lt;/FONT&gt;.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "fieldx': (?&amp;lt;fieldx&amp;gt;.*)"
| eval fieldx=split(fieldx,", ")&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 16 Nov 2022 16:41:51 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2022-11-16T16:41:51Z</dc:date>
    <item>
      <title>Trouble extracting GUIDS and how to make a new field with rex?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621099#M215910</link>
      <description>&lt;P&gt;Trying to get these UUID/GUIDs to extract from the message field. Hoping to create a rex to extract everything after 'fieldx: ' in the 8-4-4-4-12 character window separated by each , after that. Ive tried the "extract new fields " but there are well over 120 of these things and splunk doesnt like selecting all of that and filtering keeps throwing errors. And would rather not have to do this one by one.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These are embedded in the message field as stated earlier. Id like to make a new field with the rex if possible and name it "fieldx"&lt;/P&gt;
&lt;P&gt;Any and all help is welcome.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"message: Filtered marking ids for DAC property 'fieldx': abc12345-b123-c456-d789-123abx789edc, de14fc5e-22av-87dd-65d9-7563a7pleqw3, "(&amp;lt;----there are about 120 more in a row of these)&lt;/P&gt;
&lt;P&gt;Thanks in advance&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 16:33:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621099#M215910</guid>
      <dc:creator>judges88</dc:creator>
      <dc:date>2022-11-16T16:33:38Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble extracting GUIDS and how to make a new field with rex?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621103#M215911</link>
      <description>&lt;P&gt;I hope you're not trying to validate the format of each GUID with regex because that is unnecessary.&amp;nbsp; Just extract everything after "fieldx':" as-is.&amp;nbsp; If you wish, you can split the extracted field on commas so each GUID is accessible using &lt;FONT face="courier new,courier"&gt;mvindex&lt;/FONT&gt;.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "fieldx': (?&amp;lt;fieldx&amp;gt;.*)"
| eval fieldx=split(fieldx,", ")&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 16:41:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621103#M215911</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2022-11-16T16:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble extracting GUIDS and how to make a new field with rex?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621111#M215915</link>
      <description>&lt;P&gt;I would say im trying to validate the format. Just trying to take all the GUIDs ( they are all 8,4,4,4,12 ) and pull them out specifically into a new field called fieldX. I probably gave a poor description. What you gave me did work, but only if it specifies fieldX in the original message. Is there anyway to just pull out all numbers that match the 8-4-4-4-12 format into a new field?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sorry i SUCK with rex type inputs.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 17:25:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621111#M215915</guid>
      <dc:creator>judges88</dc:creator>
      <dc:date>2022-11-16T17:25:52Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble extracting GUIDS and how to make a new field with rex?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621112#M215916</link>
      <description>&lt;P&gt;The OP was pretty clear about "fieldx:" being an eye-catcher, but this command should work with or without it.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex max_match=0 "(?&amp;lt;fieldx&amp;gt;\w{8}-\w{4}-\w{4}-\w{4}-\w{12})"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 17:34:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621112#M215916</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2022-11-16T17:34:01Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble extracting GUIDS and how to make a new field with rex?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621113#M215917</link>
      <description>&lt;P&gt;Yeah this was my fault and im sorry, not trying to disrespect anyone. I posted this and found a few more logs that contain same GUIDS that dont have that fieldx as part of the message. Sorry about that. But this did work so thank you. Again SUPER new to ever trying REX dont understand 100% of it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 17:39:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621113#M215917</guid>
      <dc:creator>judges88</dc:creator>
      <dc:date>2022-11-16T17:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble extracting GUIDS and how to make a new field with rex?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621114#M215918</link>
      <description>&lt;P&gt;If you want to extract all guids after "fieldx":&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex max_match=0 "(\'fieldx\':\s)?(?&amp;lt;fieldx_guids&amp;gt;\w{8}\-\w{4}-\w{4}-\w{4}-\w{12})(?:\,\s|\")"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you want to extract all guids in the data:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex max_match=0 "(?&amp;lt;guids&amp;gt;\w{8}\-\w{4}-\w{4}-\w{4}-\w{12})"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 17:48:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trouble-extracting-GUIDS-and-how-to-make-a-new-field-with-rex/m-p/621114#M215918</guid>
      <dc:creator>johnhuang</dc:creator>
      <dc:date>2022-11-16T17:48:35Z</dc:date>
    </item>
  </channel>
</rss>

