<?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 How don't we nullify the data? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-don-t-we-nullify-the-data/m-p/457958#M129335</link>
    <description>&lt;P&gt;A developer here wrote the following - &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|eval admin_activity=if((like(cmd_data, "%audit%") AND like(cmd_data, "%start=%") AND NOT like(cmd_data, "%end=%")), "Login Attempt", NULL)
|eval admin_activity=if((like(cmd_data, "%audit%") AND like(cmd_data, "%start=%") AND like(cmd_data, "%end=%") AND isnull(admin_activity)), "Login Success", NULL)
|eval admin_activity=if((like(cmd_data, "%transaction%") AND isnull(admin_activity)), "Config Change", NULL)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We end up having &lt;CODE&gt;admin_activity&lt;/CODE&gt; only as &lt;CODE&gt;Config Change&lt;/CODE&gt; because the last &lt;CODE&gt;eval&lt;/CODE&gt; nullifies the findings from the above two &lt;CODE&gt;evals&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;What can we do here?&lt;/P&gt;</description>
    <pubDate>Wed, 21 Aug 2019 15:28:39 GMT</pubDate>
    <dc:creator>danielbb</dc:creator>
    <dc:date>2019-08-21T15:28:39Z</dc:date>
    <item>
      <title>How don't we nullify the data?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-don-t-we-nullify-the-data/m-p/457958#M129335</link>
      <description>&lt;P&gt;A developer here wrote the following - &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|eval admin_activity=if((like(cmd_data, "%audit%") AND like(cmd_data, "%start=%") AND NOT like(cmd_data, "%end=%")), "Login Attempt", NULL)
|eval admin_activity=if((like(cmd_data, "%audit%") AND like(cmd_data, "%start=%") AND like(cmd_data, "%end=%") AND isnull(admin_activity)), "Login Success", NULL)
|eval admin_activity=if((like(cmd_data, "%transaction%") AND isnull(admin_activity)), "Config Change", NULL)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We end up having &lt;CODE&gt;admin_activity&lt;/CODE&gt; only as &lt;CODE&gt;Config Change&lt;/CODE&gt; because the last &lt;CODE&gt;eval&lt;/CODE&gt; nullifies the findings from the above two &lt;CODE&gt;evals&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;What can we do here?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2019 15:28:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-don-t-we-nullify-the-data/m-p/457958#M129335</guid>
      <dc:creator>danielbb</dc:creator>
      <dc:date>2019-08-21T15:28:39Z</dc:date>
    </item>
    <item>
      <title>Re: How don't we nullify the data?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-don-t-we-nullify-the-data/m-p/457959#M129336</link>
      <description>&lt;P&gt;Merge them in single eval-case , like this, so it stops overwriting value of admin_activity after first condition is true.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|eval admin_activity=case((like(cmd_data, "%audit%") AND like(cmd_data, "%start=%") AND NOT like(cmd_data, "%end=%")), "Login Attempt", (like(cmd_data, "%audit%") AND like(cmd_data, "%start=%") AND like(cmd_data, "%end=%") AND isnull(admin_activity)), "Login Success", (like(cmd_data, "%transaction%") AND isnull(admin_activity)), "Config Change", true(), null())
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 21 Aug 2019 15:41:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-don-t-we-nullify-the-data/m-p/457959#M129336</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-08-21T15:41:32Z</dc:date>
    </item>
    <item>
      <title>Re: How don't we nullify the data?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-don-t-we-nullify-the-data/m-p/457960#M129337</link>
      <description>&lt;P&gt;hi @danielbb &lt;BR /&gt;
You need to use a single eval&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;   |eval admin_activity=if((like(cmd_data, "%audit%") AND like(cmd_data, "%start=%") AND NOT like(cmd_data, "%end=%")), "Login Attempt", if((like(cmd_data, "%audit%") AND like(cmd_data, "%start=%") AND like(cmd_data, "%end=%") AND isnull(admin_activity)), "Login Success",if((like(cmd_data, "%transaction%") AND isnull(admin_activity)), "Config Change", NULL)))
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 21 Aug 2019 15:45:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-don-t-we-nullify-the-data/m-p/457960#M129337</guid>
      <dc:creator>Sukisen1981</dc:creator>
      <dc:date>2019-08-21T15:45:01Z</dc:date>
    </item>
  </channel>
</rss>

