<?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 Data model not picking up field alias in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446653#M7185</link>
    <description>&lt;P&gt;I have installed the Suricata TA on my Splunk box.  I am verifying that the data is flowing into the Intrusion Detection data model correctly.&lt;/P&gt;

&lt;P&gt;The Suricata TA has the following field alias:&lt;/P&gt;

&lt;P&gt;FIELDALIAS-suricata_global = proto AS transport src_ip AS src dest_ip AS dest&lt;/P&gt;

&lt;P&gt;The following search shows the values of the "src" field correctly, but the "dest" field has thousands of events where "dest" is "unknown":&lt;/P&gt;

&lt;P&gt;| datamodel Intrusion_Detection Network_IDS_Attacks search &lt;/P&gt;

&lt;P&gt;But if I run this search on the raw events, I only see events that don't have the "dest" field in them:&lt;/P&gt;

&lt;P&gt;sourcetype=suricata NOT dest=*&lt;/P&gt;

&lt;P&gt;Can anyone think of a reason why two fields defined in the same FIELDALIAS- command would only have one of them populate with the values correctly?  Both the src_ip and dest_ip fields are in the events, but the data model can't see the values for dest/dest_ip for some reason...&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 20:30:19 GMT</pubDate>
    <dc:creator>responsys_cm</dc:creator>
    <dc:date>2020-09-29T20:30:19Z</dc:date>
    <item>
      <title>Data model not picking up field alias</title>
      <link>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446653#M7185</link>
      <description>&lt;P&gt;I have installed the Suricata TA on my Splunk box.  I am verifying that the data is flowing into the Intrusion Detection data model correctly.&lt;/P&gt;

&lt;P&gt;The Suricata TA has the following field alias:&lt;/P&gt;

&lt;P&gt;FIELDALIAS-suricata_global = proto AS transport src_ip AS src dest_ip AS dest&lt;/P&gt;

&lt;P&gt;The following search shows the values of the "src" field correctly, but the "dest" field has thousands of events where "dest" is "unknown":&lt;/P&gt;

&lt;P&gt;| datamodel Intrusion_Detection Network_IDS_Attacks search &lt;/P&gt;

&lt;P&gt;But if I run this search on the raw events, I only see events that don't have the "dest" field in them:&lt;/P&gt;

&lt;P&gt;sourcetype=suricata NOT dest=*&lt;/P&gt;

&lt;P&gt;Can anyone think of a reason why two fields defined in the same FIELDALIAS- command would only have one of them populate with the values correctly?  Both the src_ip and dest_ip fields are in the events, but the data model can't see the values for dest/dest_ip for some reason...&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 20:30:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446653#M7185</guid>
      <dc:creator>responsys_cm</dc:creator>
      <dc:date>2020-09-29T20:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: Data model not picking up field alias</title>
      <link>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446654#M7186</link>
      <description>&lt;P&gt;I should also add that when I ran | datamodel Certificates search, the dest field is populating properly in that datamodel.&lt;/P&gt;

&lt;P&gt;Neither datamodel is accelerated yet.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jul 2018 21:11:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446654#M7186</guid>
      <dc:creator>responsys_cm</dc:creator>
      <dc:date>2018-07-17T21:11:09Z</dc:date>
    </item>
    <item>
      <title>Re: Data model not picking up field alias</title>
      <link>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446655#M7187</link>
      <description>&lt;P&gt;Is alias' permission global?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2018 05:27:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446655#M7187</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2018-07-18T05:27:39Z</dc:date>
    </item>
    <item>
      <title>Re: Data model not picking up field alias</title>
      <link>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446656#M7188</link>
      <description>&lt;P&gt;I know its an old post but i had the same problem-&lt;BR /&gt;
Solution was that i extracted all my fields using a delims transforms on a dedicated field extraction (basically the _raw event without header data). Now the datamodel was not aware of the underlying field extraction. Adding it as a field of the datamodel did the trick and all other fields showed up.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2019 11:45:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446656#M7188</guid>
      <dc:creator>claudio_manig</dc:creator>
      <dc:date>2019-02-12T11:45:48Z</dc:date>
    </item>
    <item>
      <title>Re: Data model not picking up field alias</title>
      <link>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446657#M7189</link>
      <description>&lt;P&gt;I have the same problem Suricata 2.3.3: &lt;BR /&gt;
FIELDALIAS-suricata_global = proto AS transport src_ip AS src dest_ip AS dest &lt;BR /&gt;
The alias is not adding dest to the logs that are tagged with tag=attack OR tag=ids.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:57:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Data-model-not-picking-up-field-alias/m-p/446657#M7189</guid>
      <dc:creator>zschmerber</dc:creator>
      <dc:date>2020-09-30T00:57:41Z</dc:date>
    </item>
  </channel>
</rss>

