<?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: automatic lookups in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42147#M9814</link>
    <description>&lt;P&gt;Did that - doesn't work. &lt;/P&gt;

&lt;P&gt;LOOKUP-hostdb = hostdb_lookup  srcIP OUTPUTNEW deviceName&lt;/P&gt;</description>
    <pubDate>Wed, 02 May 2012 21:33:55 GMT</pubDate>
    <dc:creator>a212830</dc:creator>
    <dc:date>2012-05-02T21:33:55Z</dc:date>
    <item>
      <title>automatic lookups</title>
      <link>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42145#M9812</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I configured a lookup that works fine, if I explicitly use the lookup statement in my search, but I want the field to auto-populate, based upon the sourcetype. Is there a way to do this? &lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2012 20:43:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42145#M9812</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2012-05-02T20:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: automatic lookups</title>
      <link>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42146#M9813</link>
      <description>&lt;P&gt;Yes, you set this in props.conf using the LOOKUP directive. For instance&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[mysourcetype]
LOOKUP-foo = mylookuptable somefield OUTPUT somelookedupfield
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3/admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/4.3/admin/Propsconf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2012 21:01:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42146#M9813</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-05-02T21:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: automatic lookups</title>
      <link>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42147#M9814</link>
      <description>&lt;P&gt;Did that - doesn't work. &lt;/P&gt;

&lt;P&gt;LOOKUP-hostdb = hostdb_lookup  srcIP OUTPUTNEW deviceName&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2012 21:33:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42147#M9814</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2012-05-02T21:33:55Z</dc:date>
    </item>
    <item>
      <title>Re: automatic lookups</title>
      <link>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42148#M9815</link>
      <description>&lt;P&gt;As Ayn states, this can be done with a LOOKUP-statement in props.conf, but you also need the corresponding transforms.conf stanza to make it work. I recently posted an answer to this type of question;&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/5916/using-cidr-in-a-lookup-table?page=1&amp;amp;focusedAnswerId=46866#46866"&gt;http://splunk-base.splunk.com/answers/5916/using-cidr-in-a-lookup-table?page=1&amp;amp;focusedAnswerId=46866#46866&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Have a look, and if you don't figure it out, feel free to provide more information regarding what you're trying to do.&lt;/P&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2012 21:53:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42148#M9815</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-05-02T21:53:20Z</dc:date>
    </item>
    <item>
      <title>Re: automatic lookups</title>
      <link>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42149#M9816</link>
      <description>&lt;P&gt;needs restart to make it work?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2016 14:39:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/automatic-lookups/m-p/42149#M9816</guid>
      <dc:creator>AllenZhang</dc:creator>
      <dc:date>2016-01-27T14:39:44Z</dc:date>
    </item>
  </channel>
</rss>

