<?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 for Dell Quest TPAM logs ? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Regex-for-Dell-Quest-TPAM-logs/m-p/304466#M91529</link>
    <description>&lt;P&gt;Hey @plarsenDST, can you accept the Answer if it worked? You and Rich will both receive karma points that way! &lt;/P&gt;</description>
    <pubDate>Tue, 29 Aug 2017 19:37:28 GMT</pubDate>
    <dc:creator>lfedak_splunk</dc:creator>
    <dc:date>2017-08-29T19:37:28Z</dc:date>
    <item>
      <title>Regex for Dell Quest TPAM logs ?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Regex-for-Dell-Quest-TPAM-logs/m-p/304463#M91526</link>
      <description>&lt;P&gt;Has anyone done any work with Dell/Quest TPAM logs?  Not enough experience with regex to know where to start.&lt;/P&gt;

&lt;P&gt;As an example for UserName:  sometimes it is one word sometimes it is two words so having Splunk Build the regex does not work real well.&lt;/P&gt;

&lt;P&gt;Trying to learn so what kind of Regex will take next word or two words before it see's another word with a trailing colon: which would be the next key pair, like Operation:  or ObjectType: in the log examples below. &lt;/P&gt;

&lt;P&gt;Aug 22 03:41:41 TPAMHOST1 PAR[72]: Source: TPAMCONSOLE UserName: &lt;STRONG&gt;Automation Engine&lt;/STRONG&gt; Operation: Timed Out ObjectType: Authenticated Session Target: id12345 Role: N/A Failed? 0 OtherInfo: Inactive for 40 minutes&lt;/P&gt;

&lt;P&gt;Aug 22 03:29:19 TPAMHOST1 PAR[61]: Source: TPAMCONSOLE UserName: &lt;STRONG&gt;id12345&lt;/STRONG&gt; Operation: Logout ObjectType: Authentication Target: id12345 Role: N/A Failed? 0 OtherInfo: Inactive for 14 seconds. From address 10.10.10.10&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 12:43:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Regex-for-Dell-Quest-TPAM-logs/m-p/304463#M91526</guid>
      <dc:creator>plarsenDST</dc:creator>
      <dc:date>2017-08-29T12:43:17Z</dc:date>
    </item>
    <item>
      <title>Re: Regex for Dell Quest TPAM logs ?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Regex-for-Dell-Quest-TPAM-logs/m-p/304464#M91527</link>
      <description>&lt;P&gt;Use the keyword that follows as a delimiter.  See if this regex helps.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Source:\s(?&amp;lt;Source&amp;gt;.*?)\sUserName:\s(?&amp;lt;UserName&amp;gt;.*?)\sOperation:\s(?&amp;lt;Operation&amp;gt;.*?)\sObjectType:\s(?&amp;lt;ObjectType&amp;gt;.*?)\sTarget:(?&amp;lt;Target&amp;gt;.*?)\sRole:\s(?&amp;lt;Role&amp;gt;.*?)\sFailed\?(?&amp;lt;Failed&amp;gt;.*?)\sOtherInfo:\s(?&amp;lt;OtherInfo&amp;gt;.*)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 29 Aug 2017 15:54:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Regex-for-Dell-Quest-TPAM-logs/m-p/304464#M91527</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2017-08-29T15:54:40Z</dc:date>
    </item>
    <item>
      <title>Re: Regex for Dell Quest TPAM logs ?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Regex-for-Dell-Quest-TPAM-logs/m-p/304465#M91528</link>
      <description>&lt;P&gt;Thanks for the help.&lt;/P&gt;

&lt;P&gt;Removed the &lt;CODE&gt;\sFailed\?(?&amp;lt;Failed&amp;gt;.*?)&lt;/CODE&gt; part as that was the Role: value.  So the rest is as you provided which seems to be doing what it is supposed to.&lt;/P&gt;

&lt;P&gt;Thanks again.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Source:\s(?&amp;lt;Source&amp;gt;.*?)\sUserName:\s(?&amp;lt;UserName&amp;gt;.*?)\sOperation:\s(?&amp;lt;Operation&amp;gt;.*?)\sObjectType:\s(?&amp;lt;ObjectType&amp;gt;.*?)\sTarget:(?&amp;lt;Target&amp;gt;.*?)\sRole:\s(?&amp;lt;Role&amp;gt;.*?)\sOtherInfo:\s(?&amp;lt;OtherInfo&amp;gt;.*)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 29 Aug 2017 18:32:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Regex-for-Dell-Quest-TPAM-logs/m-p/304465#M91528</guid>
      <dc:creator>plarsenDST</dc:creator>
      <dc:date>2017-08-29T18:32:35Z</dc:date>
    </item>
    <item>
      <title>Re: Regex for Dell Quest TPAM logs ?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Regex-for-Dell-Quest-TPAM-logs/m-p/304466#M91529</link>
      <description>&lt;P&gt;Hey @plarsenDST, can you accept the Answer if it worked? You and Rich will both receive karma points that way! &lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 19:37:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Regex-for-Dell-Quest-TPAM-logs/m-p/304466#M91529</guid>
      <dc:creator>lfedak_splunk</dc:creator>
      <dc:date>2017-08-29T19:37:28Z</dc:date>
    </item>
  </channel>
</rss>

