<?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 Confusing behaviour of fieldalias in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Confusing-behaviour-of-fieldalias/m-p/343989#M101904</link>
    <description>&lt;P&gt;I've have downloaded from Splunkbase and applied the Linux secure TA on my Splunk instance, and I've been facing with a strange issue I can't understand.&lt;/P&gt;

&lt;P&gt;There are a couple fieldaliases defined in it:&lt;/P&gt;

&lt;P&gt;FIELDALIAS-rhost = rhost AS src_ip    &amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;
FIELDALIAS-src_user = ruser AS src_user&lt;BR /&gt;
FIELDALIAS-app = process AS app&lt;BR /&gt;
FIELDALIAS-vendor_product = process AS vendor_product&lt;BR /&gt;
FIELDALIAS-dest = host AS dest&lt;BR /&gt;
FIELDALIAS-dest_host = host AS dest_host&lt;BR /&gt;
FIELDALIAS-dest_nt_domain = kerberos_domain AS dest_nt_domain&lt;BR /&gt;
FIELDALIAS-src = src_ip AS src  &amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;/P&gt;

&lt;P&gt;I've marked the problematic ones with the arrows.&lt;BR /&gt;
So, src_ip is created just as expected. However, src is not, just only in a really few number of events. Doing a quick spotcheck, I had like 25 different values in src_ip, but only 2 in src.&lt;BR /&gt;
My search looked like simply this:&lt;BR /&gt;
index=ftp&lt;/P&gt;

&lt;P&gt;Going forward, when I've selected a value from src_ip, and run my search like this:&lt;BR /&gt;
index=ftp src_ip=1.2.3.4&lt;/P&gt;

&lt;P&gt;then the src field was created, and it had the 1.2.3.4 value in it. (previously, it was present in src_ip but not in src)&lt;/P&gt;

&lt;P&gt;After this, I've created a new props.conf in the local folder of the TA, and added the following line:&lt;BR /&gt;
FIELDALIAS-rhost = rhost AS src_ip&lt;BR /&gt;
FIELDALIAS-rhost_test= rhost AS src &amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;/P&gt;

&lt;P&gt;Now it works for 100% of the events, both src_ip and src is created with all the values.&lt;/P&gt;

&lt;P&gt;I just can't understand what went wrong with the original configuration. &lt;BR /&gt;
What am I missing ?&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 13:47:33 GMT</pubDate>
    <dc:creator>szabados</dc:creator>
    <dc:date>2020-09-29T13:47:33Z</dc:date>
    <item>
      <title>Confusing behaviour of fieldalias</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Confusing-behaviour-of-fieldalias/m-p/343989#M101904</link>
      <description>&lt;P&gt;I've have downloaded from Splunkbase and applied the Linux secure TA on my Splunk instance, and I've been facing with a strange issue I can't understand.&lt;/P&gt;

&lt;P&gt;There are a couple fieldaliases defined in it:&lt;/P&gt;

&lt;P&gt;FIELDALIAS-rhost = rhost AS src_ip    &amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;
FIELDALIAS-src_user = ruser AS src_user&lt;BR /&gt;
FIELDALIAS-app = process AS app&lt;BR /&gt;
FIELDALIAS-vendor_product = process AS vendor_product&lt;BR /&gt;
FIELDALIAS-dest = host AS dest&lt;BR /&gt;
FIELDALIAS-dest_host = host AS dest_host&lt;BR /&gt;
FIELDALIAS-dest_nt_domain = kerberos_domain AS dest_nt_domain&lt;BR /&gt;
FIELDALIAS-src = src_ip AS src  &amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;/P&gt;

&lt;P&gt;I've marked the problematic ones with the arrows.&lt;BR /&gt;
So, src_ip is created just as expected. However, src is not, just only in a really few number of events. Doing a quick spotcheck, I had like 25 different values in src_ip, but only 2 in src.&lt;BR /&gt;
My search looked like simply this:&lt;BR /&gt;
index=ftp&lt;/P&gt;

&lt;P&gt;Going forward, when I've selected a value from src_ip, and run my search like this:&lt;BR /&gt;
index=ftp src_ip=1.2.3.4&lt;/P&gt;

&lt;P&gt;then the src field was created, and it had the 1.2.3.4 value in it. (previously, it was present in src_ip but not in src)&lt;/P&gt;

&lt;P&gt;After this, I've created a new props.conf in the local folder of the TA, and added the following line:&lt;BR /&gt;
FIELDALIAS-rhost = rhost AS src_ip&lt;BR /&gt;
FIELDALIAS-rhost_test= rhost AS src &amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;/P&gt;

&lt;P&gt;Now it works for 100% of the events, both src_ip and src is created with all the values.&lt;/P&gt;

&lt;P&gt;I just can't understand what went wrong with the original configuration. &lt;BR /&gt;
What am I missing ?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 13:47:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Confusing-behaviour-of-fieldalias/m-p/343989#M101904</guid>
      <dc:creator>szabados</dc:creator>
      <dc:date>2020-09-29T13:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: Confusing behaviour of fieldalias</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Confusing-behaviour-of-fieldalias/m-p/343990#M101905</link>
      <description>&lt;P&gt;In your original configuration, you are trying to define a fieldalias &lt;CODE&gt;src&lt;/CODE&gt; from the other fieldalias &lt;CODE&gt;src_ip&lt;/CODE&gt;. That is no supported. All fieldalias operation happen in parallel, so you cannot have a dependency on one alias in the definition of another alias.&lt;/P&gt;

&lt;P&gt;Your second version works because there is no dependency on &lt;CODE&gt;src_ip&lt;/CODE&gt; in the definition of &lt;CODE&gt;src&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Apr 2017 10:52:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Confusing-behaviour-of-fieldalias/m-p/343990#M101905</guid>
      <dc:creator>rjthibod</dc:creator>
      <dc:date>2017-04-24T10:52:23Z</dc:date>
    </item>
    <item>
      <title>Re: Confusing behaviour of fieldalias</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Confusing-behaviour-of-fieldalias/m-p/343991#M101906</link>
      <description>&lt;P&gt;For a more in-depth explanation of the limitations of FIELDALIAS, please see my answer on &lt;A href="https://answers.splunk.com/answers/657473/fieldalias-override-another-fieldalias.html?childToView=762283#answer-762283"&gt;https://answers.splunk.com/answers/657473/fieldalias-override-another-fieldalias.html?childToView=762283#answer-762283&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 23:07:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Confusing-behaviour-of-fieldalias/m-p/343991#M101906</guid>
      <dc:creator>lwest_splunk</dc:creator>
      <dc:date>2019-08-01T23:07:53Z</dc:date>
    </item>
  </channel>
</rss>

