<?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 lookup in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/lookup/m-p/559962#M6442</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In lookup definition,&lt;/P&gt;&lt;P&gt;IT_server_list is created in lookup definition which is mapped to CSV named (server_list.csv)&lt;/P&gt;&lt;P&gt;In Lookup Table,&lt;/P&gt;&lt;P&gt;server_list.csv file is there&lt;/P&gt;&lt;P&gt;In automatic lookup,&lt;/P&gt;&lt;P&gt;IT_server_list is created&lt;/P&gt;&lt;P&gt;why do we need automatic lookup?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jul 2021 03:48:04 GMT</pubDate>
    <dc:creator>VijaySrrie</dc:creator>
    <dc:date>2021-07-19T03:48:04Z</dc:date>
    <item>
      <title>lookup</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/lookup/m-p/559962#M6442</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In lookup definition,&lt;/P&gt;&lt;P&gt;IT_server_list is created in lookup definition which is mapped to CSV named (server_list.csv)&lt;/P&gt;&lt;P&gt;In Lookup Table,&lt;/P&gt;&lt;P&gt;server_list.csv file is there&lt;/P&gt;&lt;P&gt;In automatic lookup,&lt;/P&gt;&lt;P&gt;IT_server_list is created&lt;/P&gt;&lt;P&gt;why do we need automatic lookup?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jul 2021 03:48:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/lookup/m-p/559962#M6442</guid>
      <dc:creator>VijaySrrie</dc:creator>
      <dc:date>2021-07-19T03:48:04Z</dc:date>
    </item>
    <item>
      <title>Re: lookup</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/lookup/m-p/559964#M6443</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;Your transforms.conf should be having lookup definition, that is enough for you to run | lookup command in UI.&lt;/P&gt;&lt;P&gt;What if the search events to be enriched automatically by adding additional field when someone search the sourcetype/host/source. Then props.conf automatic lookup LOOKUP-&amp;lt;class&amp;gt;=&amp;nbsp; syntax works.&lt;/P&gt;&lt;P&gt;Docs says:&amp;nbsp;&lt;SPAN&gt;you can optionally create an additional&amp;nbsp;&lt;/SPAN&gt;props.conf&lt;SPAN&gt;&amp;nbsp;configuration that makes the lookup "automatic." This means that it runs in the background at search time and automatically adds output fields to events that have the correct match fields.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Splunk user doesn't need to use | lookup command everytime, if automatic lookup been configured one time. Refer -&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.1/Knowledge/Makeyourlookupautomatic" target="_blank" rel="noopener"&gt;Make your lookup automatic - Splunk Documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;An upvote would be appreciated and Accept solution if this reply helps!&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jul 2021 04:09:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/lookup/m-p/559964#M6443</guid>
      <dc:creator>venkatasri</dc:creator>
      <dc:date>2021-07-19T04:09:18Z</dc:date>
    </item>
  </channel>
</rss>

