<?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: How to write a Regex to capture the Path(\Απεσταλμένα) and Subject (TYPICAL MAIN SHELF)? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-write-a-Regex-to-capture-the-Path-%CE%91%CF%80%CE%B5%CF%83%CF%84%CE%B1%CE%BB%CE%BC%CE%AD%CE%BD%CE%B1-and-Subject/m-p/610405#M212266</link>
    <description>&lt;P&gt;It depends on what the data really looks like - the .* part of the Subject capture will capture everything up to a line terminator. You data _implies_ that the text is on multiple lines, but it looks like you've pasted that from a JSON viewer, which is interpreting your data - particularly as there are no visible quotes, which would be expected in JSON.&lt;/P&gt;&lt;P&gt;Can you show the RAW field rather than this formatted one.&lt;/P&gt;&lt;P&gt;The .* capture part of the field may probably be better written as&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[^\"]*&lt;/LI-CODE&gt;&lt;P&gt;i.e. capture up to a terminating quotation character. However, it also may be that the JSON can be parsed directly with spath - depending on what fields are extracted&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Aug 2022 23:36:52 GMT</pubDate>
    <dc:creator>bowesmana</dc:creator>
    <dc:date>2022-08-22T23:36:52Z</dc:date>
    <item>
      <title>How to write a Regex to capture the Path(\Απεσταλμένα) and Subject (TYPICAL MAIN SHELF)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-write-a-Regex-to-capture-the-Path-%CE%91%CF%80%CE%B5%CF%83%CF%84%CE%B1%CE%BB%CE%BC%CE%AD%CE%BD%CE%B1-and-Subject/m-p/610373#M212253</link>
      <description>&lt;P&gt;I want to capture the Path (\Απεσταλμένα) and Subject (TYPICAL MAIN SHELF) .&amp;nbsp; I am using below regex Subject\W\s(?&amp;lt;Subject&amp;gt;.*)&amp;nbsp; and&amp;nbsp;&lt;/P&gt;
&lt;P&gt;rex "Path\W\s(?&amp;lt;Path&amp;gt;\W.*)"&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But these are not working . It is not capturing the path while for subject it is capturing many more lines which are not required .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Someone please help&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;PH0PR07MB8510A5DC1014429F3B411EB1E39B9@PH0PR07MB8510.namprd07.prod.outlook.com&amp;gt;&lt;BR /&gt;IsRecord: false&lt;BR /&gt;ParentFolder: { [-]&lt;BR /&gt;Id: LgAAAACYR3ou5YLkQLdwhKR5o0aGAQDzGy/hF08sRpmozaW+A2HqAAAAdHcNAAAB&lt;BR /&gt;Path: \Απεσταλμένα&lt;BR /&gt;}&lt;BR /&gt;SizeInBytes: 180998&lt;BR /&gt;Subject: TYPICAL MAIN SHELF&lt;BR /&gt;}&lt;BR /&gt;LogonType: 0&lt;BR /&gt;LogonUserSid: S-1-5-21-2050334910-350505970-4048673702-5100548&lt;BR /&gt;MailboxGuid: 967cf2f1-6b52-4e79-bf98-1hnfj55667&lt;BR /&gt;MailboxOwnerSid: S-1-5-21-2050334910-350505970-499886553&lt;/P&gt;</description>
      <pubDate>Mon, 22 Aug 2022 19:14:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-write-a-Regex-to-capture-the-Path-%CE%91%CF%80%CE%B5%CF%83%CF%84%CE%B1%CE%BB%CE%BC%CE%AD%CE%BD%CE%B1-and-Subject/m-p/610373#M212253</guid>
      <dc:creator>biswa2112</dc:creator>
      <dc:date>2022-08-22T19:14:09Z</dc:date>
    </item>
    <item>
      <title>Re: How to write a Regex to capture the Path(\Απεσταλμένα) and Subject (TYPICAL MAIN SHELF)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-write-a-Regex-to-capture-the-Path-%CE%91%CF%80%CE%B5%CF%83%CF%84%CE%B1%CE%BB%CE%BC%CE%AD%CE%BD%CE%B1-and-Subject/m-p/610405#M212266</link>
      <description>&lt;P&gt;It depends on what the data really looks like - the .* part of the Subject capture will capture everything up to a line terminator. You data _implies_ that the text is on multiple lines, but it looks like you've pasted that from a JSON viewer, which is interpreting your data - particularly as there are no visible quotes, which would be expected in JSON.&lt;/P&gt;&lt;P&gt;Can you show the RAW field rather than this formatted one.&lt;/P&gt;&lt;P&gt;The .* capture part of the field may probably be better written as&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[^\"]*&lt;/LI-CODE&gt;&lt;P&gt;i.e. capture up to a terminating quotation character. However, it also may be that the JSON can be parsed directly with spath - depending on what fields are extracted&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Aug 2022 23:36:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-write-a-Regex-to-capture-the-Path-%CE%91%CF%80%CE%B5%CF%83%CF%84%CE%B1%CE%BB%CE%BC%CE%AD%CE%BD%CE%B1-and-Subject/m-p/610405#M212266</guid>
      <dc:creator>bowesmana</dc:creator>
      <dc:date>2022-08-22T23:36:52Z</dc:date>
    </item>
  </channel>
</rss>

