<?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: Help with Rex Field Extraction in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Help-with-Rex-Field-Extraction/m-p/668009#M229193</link>
    <description>&lt;P&gt;Add in the \r\n to the regex, i.e.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "Registrar:\s(?&amp;lt;registrar&amp;gt;.*?)\\\r\\\n Registrar IANA"&lt;/LI-CODE&gt;&lt;P&gt;Note 3 slashes&lt;/P&gt;&lt;P&gt;I assume those \r\n are literal characters rather than CR/LF?&lt;/P&gt;</description>
    <pubDate>Thu, 09 Nov 2023 03:48:06 GMT</pubDate>
    <dc:creator>bowesmana</dc:creator>
    <dc:date>2023-11-09T03:48:06Z</dc:date>
    <item>
      <title>Help with Rex Field Extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-with-Rex-Field-Extraction/m-p/668008#M229192</link>
      <description>&lt;P&gt;I am trying to write a rex command that extracts the field "registrar" from the below four event examples. The below values in &lt;STRONG&gt;bold&lt;/STRONG&gt; are what i am looking for to be the value for "registrar".&amp;nbsp; I am using the following regex to extract the field and values, but i seem to be capturing the \r\n after the bold values as well.&amp;nbsp; How can i modify my regex to capture just the company name in &lt;STRONG&gt;bold&lt;/STRONG&gt; leading up to \r\n&amp;nbsp;Registrar IANA&lt;/P&gt;&lt;P&gt;&lt;U&gt;Current regex being used:&lt;/U&gt;&amp;nbsp; &amp;nbsp;&lt;EM&gt;Registrar:\s(?&amp;lt;registrar&amp;gt;.*?) Registrar IANA&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Expiry Date: 2026-12-09T15:18:58Z\r\n Registrar:&amp;nbsp;&lt;STRONG&gt;ABC Holdings, Inc&lt;/STRONG&gt;.\r\n Registrar IANA ID: 972&lt;/P&gt;&lt;P&gt;Expiry Date: 2026-12-09T15:18:58Z\r\n Registrar: &lt;STRONG&gt;Gamer.com, LLC&lt;/STRONG&gt;\r\n Registrar IANA ID: 837&lt;/P&gt;&lt;P&gt;Expiry Date: 2026-12-09T15:18:59Z\r\n Registrar: &lt;STRONG&gt;NoCo MFR Ltd.&lt;/STRONG&gt;\r\n Registrar IANA ID: 756&lt;/P&gt;&lt;P&gt;Expiry Date: 2026-12-09T15:18:59Z\r\n Registrar: &lt;STRONG&gt;Onetrust Group, INC&lt;/STRONG&gt;\r\n Registrar IANA ID: 478&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 03:24:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-with-Rex-Field-Extraction/m-p/668008#M229192</guid>
      <dc:creator>scout29</dc:creator>
      <dc:date>2023-11-09T03:24:02Z</dc:date>
    </item>
    <item>
      <title>Re: Help with Rex Field Extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-with-Rex-Field-Extraction/m-p/668009#M229193</link>
      <description>&lt;P&gt;Add in the \r\n to the regex, i.e.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "Registrar:\s(?&amp;lt;registrar&amp;gt;.*?)\\\r\\\n Registrar IANA"&lt;/LI-CODE&gt;&lt;P&gt;Note 3 slashes&lt;/P&gt;&lt;P&gt;I assume those \r\n are literal characters rather than CR/LF?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 03:48:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-with-Rex-Field-Extraction/m-p/668009#M229193</guid>
      <dc:creator>bowesmana</dc:creator>
      <dc:date>2023-11-09T03:48:06Z</dc:date>
    </item>
    <item>
      <title>Re: Help with Rex Field Extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-with-Rex-Field-Extraction/m-p/668012#M229194</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/261177"&gt;@scout29&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;please try this:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "Registrar:\s+(?&amp;lt;Registrar&amp;gt;[^\\]*)"&lt;/LI-CODE&gt;&lt;P&gt;that you can test at&amp;nbsp;&lt;A href="https://regex101.com/r/7PdpcJ/1" target="_blank"&gt;https://regex101.com/r/7PdpcJ/1&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If it doesn't run on Splunk use three backslashes in the square parenthesis (sometimes Splunk is strange in regex extractions!).&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 07:08:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-with-Rex-Field-Extraction/m-p/668012#M229194</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2023-11-09T07:08:21Z</dc:date>
    </item>
    <item>
      <title>Re: Help with Rex Field Extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-with-Rex-Field-Extraction/m-p/668428#M229312</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/261177"&gt;@scout29&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;good for you, see next time!&lt;/P&gt;&lt;P&gt;Ciao and happy splunking&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;P&gt;P.S.: Karma Points are appreciated by all the contributors &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Nov 2023 14:18:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-with-Rex-Field-Extraction/m-p/668428#M229312</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2023-11-13T14:18:29Z</dc:date>
    </item>
  </channel>
</rss>

