<?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: Can you have cascading automatic lookups? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Can-you-have-cascading-automatic-lookups/m-p/272804#M82136</link>
    <description>&lt;P&gt;Thanks for the link, I somehow managed to miss that. I'll take a look then.&lt;/P&gt;</description>
    <pubDate>Tue, 09 Feb 2016 09:03:17 GMT</pubDate>
    <dc:creator>danielpellarini</dc:creator>
    <dc:date>2016-02-09T09:03:17Z</dc:date>
    <item>
      <title>Can you have cascading automatic lookups?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Can-you-have-cascading-automatic-lookups/m-p/272802#M82134</link>
      <description>&lt;P&gt;In some of my sourcetypes, I am using automatic CSV lookups to add some data to Splunk (as explained in the docs &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.0/Knowledge/Addfieldsfromexternaldatasources"&gt;here&lt;/A&gt;).&lt;/P&gt;

&lt;P&gt;However, can I have a second automatic lookup over &lt;EM&gt;data that was already added with an automatic lookup&lt;/EM&gt;? I am using the same method as above but it looks like it's not working.&lt;/P&gt;

&lt;P&gt;Just to clarify, as an example, suppose I have the &lt;STRONG&gt;UserID&lt;/STRONG&gt; field, I then have an automatic lookup that adds the user's birth town to Splunk, can I now have an automatic lookup that adds the country of birth starting from the birth town?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Feb 2016 17:32:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Can-you-have-cascading-automatic-lookups/m-p/272802#M82134</guid>
      <dc:creator>danielpellarini</dc:creator>
      <dc:date>2016-02-08T17:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: Can you have cascading automatic lookups?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Can-you-have-cascading-automatic-lookups/m-p/272803#M82135</link>
      <description>&lt;P&gt;Yes, this is possible. You need to name your lookups appropriately, because they are evaluated in alphabetical order. See &lt;A href="https://answers.splunk.com/answers/209148/can-you-perform-an-automatic-lookup-based-on-the-o.html"&gt;here&lt;/A&gt; for an older question about this.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Feb 2016 08:52:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Can-you-have-cascading-automatic-lookups/m-p/272803#M82135</guid>
      <dc:creator>jeffland</dc:creator>
      <dc:date>2016-02-09T08:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: Can you have cascading automatic lookups?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Can-you-have-cascading-automatic-lookups/m-p/272804#M82136</link>
      <description>&lt;P&gt;Thanks for the link, I somehow managed to miss that. I'll take a look then.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Feb 2016 09:03:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Can-you-have-cascading-automatic-lookups/m-p/272804#M82136</guid>
      <dc:creator>danielpellarini</dc:creator>
      <dc:date>2016-02-09T09:03:17Z</dc:date>
    </item>
    <item>
      <title>Re: Can you have cascading automatic lookups?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Can-you-have-cascading-automatic-lookups/m-p/272805#M82137</link>
      <description>&lt;P&gt;wha t is automatic lookup ,how do I heck my lookup is setup correctly for automatic lookup .&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 13:52:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Can-you-have-cascading-automatic-lookups/m-p/272805#M82137</guid>
      <dc:creator>rajneeshc1981</dc:creator>
      <dc:date>2018-08-06T13:52:34Z</dc:date>
    </item>
  </channel>
</rss>

