<?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 Standardizing Account_Name for Event 4769 to match others? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Standardizing-Account-Name-for-Event-4769-to-match-others/m-p/131397#M35840</link>
    <description>&lt;P&gt;I'm trying to use EventCode 4769 along with several other EventCodes in a search and am running into the problem that for this code all the Account_Name fields contain the fully qualified name (name@domain) while the other fields are just the name.  I need to somehow need to get the Account_Name field for this code only, to stop reading at the @ sign. &lt;/P&gt;

&lt;P&gt;Any thoughts would be greatly appreciated!  Thank you!&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 16:23:15 GMT</pubDate>
    <dc:creator>kearaspoor</dc:creator>
    <dc:date>2020-09-28T16:23:15Z</dc:date>
    <item>
      <title>Standardizing Account_Name for Event 4769 to match others?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Standardizing-Account-Name-for-Event-4769-to-match-others/m-p/131397#M35840</link>
      <description>&lt;P&gt;I'm trying to use EventCode 4769 along with several other EventCodes in a search and am running into the problem that for this code all the Account_Name fields contain the fully qualified name (name@domain) while the other fields are just the name.  I need to somehow need to get the Account_Name field for this code only, to stop reading at the @ sign. &lt;/P&gt;

&lt;P&gt;Any thoughts would be greatly appreciated!  Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:23:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Standardizing-Account-Name-for-Event-4769-to-match-others/m-p/131397#M35840</guid>
      <dc:creator>kearaspoor</dc:creator>
      <dc:date>2020-09-28T16:23:15Z</dc:date>
    </item>
    <item>
      <title>Re: Standardizing Account_Name for Event 4769 to match others?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Standardizing-Account-Name-for-Event-4769-to-match-others/m-p/131398#M35841</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;| rex field=Account_Name "(?&amp;lt;Account_Name&amp;gt;[^@]+)"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 14 Apr 2014 23:01:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Standardizing-Account-Name-for-Event-4769-to-match-others/m-p/131398#M35841</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2014-04-14T23:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: Standardizing Account_Name for Event 4769 to match others?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Standardizing-Account-Name-for-Event-4769-to-match-others/m-p/131399#M35842</link>
      <description>&lt;P&gt;Thank you! That was exactly what I needed!&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jun 2014 20:22:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Standardizing-Account-Name-for-Event-4769-to-match-others/m-p/131399#M35842</guid>
      <dc:creator>kearaspoor</dc:creator>
      <dc:date>2014-06-16T20:22:02Z</dc:date>
    </item>
  </channel>
</rss>

