<?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: Calculated field in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field/m-p/689645#M234990</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/164779"&gt;@VijaySrrie&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;they should work also using three different calculated fields, anyway, you could nest the conditions from the other calculated fields, even if the final caculated fied will be longer:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval action=
case(error="invalid credentials", "failure", ((like('request.path',"auth/ldap/login/%") OR like('request.path',"auth/ldapco/login/%")) AND (NOT error="invalid credentials")) OR (like('request.path',"auth/token/lookup-self") AND ('auth.display_name'="root")) ,"success")

| eval app=case(action="success" OR action="failure", "appname_Authentication")

| eval valid=if(error="invalid credentials","Error","Success")&lt;/LI-CODE&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Wed, 05 Jun 2024 06:11:50 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2024-06-05T06:11:50Z</dc:date>
    <item>
      <title>Calculated field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field/m-p/689626#M234984</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;I need to create 3 calculated fields&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;| eval action=

case(error="invalid credentials", "failure", ((like('request.path',"auth/ldap/login/%") OR like('request.path',"auth/ldapco/login/%")) AND (valid="Success")) OR (like('request.path',"auth/token/lookup-self") AND ('auth.display_name'="root")) ,"success")

| eval app=

case(action="success" OR action="failure", "appname_Authentication")

| eval valid=

if(error="invalid credentials","Error","Success")&lt;/LI-CODE&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;action field is dependant on valid&lt;BR /&gt;app field is dependant on action&lt;BR /&gt;&lt;BR /&gt;I am unable to see app field in the splunk, may I know how to create it?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2024 09:55:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Calculated-field/m-p/689626#M234984</guid>
      <dc:creator>VijaySrrie</dc:creator>
      <dc:date>2024-06-05T09:55:51Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated field</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Calculated-field/m-p/689645#M234990</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/164779"&gt;@VijaySrrie&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;they should work also using three different calculated fields, anyway, you could nest the conditions from the other calculated fields, even if the final caculated fied will be longer:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval action=
case(error="invalid credentials", "failure", ((like('request.path',"auth/ldap/login/%") OR like('request.path',"auth/ldapco/login/%")) AND (NOT error="invalid credentials")) OR (like('request.path',"auth/token/lookup-self") AND ('auth.display_name'="root")) ,"success")

| eval app=case(action="success" OR action="failure", "appname_Authentication")

| eval valid=if(error="invalid credentials","Error","Success")&lt;/LI-CODE&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2024 06:11:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Calculated-field/m-p/689645#M234990</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-06-05T06:11:50Z</dc:date>
    </item>
  </channel>
</rss>

