<?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: Using inputlookup with external_cmd in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342425#M5322</link>
    <description>&lt;P&gt;Yup the docs feedback is the best way to get Splunk to update the docs. The docs team watches it carefully.&lt;/P&gt;</description>
    <pubDate>Wed, 08 Mar 2017 13:25:52 GMT</pubDate>
    <dc:creator>starcher</dc:creator>
    <dc:date>2017-03-08T13:25:52Z</dc:date>
    <item>
      <title>Using inputlookup with external_cmd</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342420#M5317</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;Is it possible to use &lt;EM&gt;inputlookup&lt;/EM&gt; to pull a list of information from a scripted lookup?&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/SearchReference/Inputlookup#Required_arguments"&gt;The documentation&lt;/A&gt; for &lt;EM&gt;inputlookup&lt;/EM&gt; seems to suggest this is possible:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;The lookup table can be configured for any lookup type (CSV, external, or KV store)._&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;But &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/Knowledge/Configureexternallookups#About_the_external_lookup_script"&gt;the documentation&lt;/A&gt; for transforms.conf where the scripted input is defined states&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;Your external lookup script must take in a partially empty CSV file and output a filled-in CSV file&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;Which implies that it can't be used with a generating command like inputlookup.&lt;/P&gt;

&lt;P&gt;I'm trying to pull in a CSV from a threat intel feed but in a way that would allow me to do so using a scheduled search rather than a scripted input or modular input. Any thoughts on how best to do this if using a scripted input with inputlook isn't possible?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2017 23:45:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342420#M5317</guid>
      <dc:creator>cygnetix</dc:creator>
      <dc:date>2017-03-07T23:45:45Z</dc:date>
    </item>
    <item>
      <title>Re: Using inputlookup with external_cmd</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342421#M5318</link>
      <description>&lt;P&gt;Search logs show:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;03-08-2017 10:20:03.398 WARN  SearchOperator:inputcsv - sid:1488932400.14 The lookup table 'testlookup' is invalid.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;So it looks like, possibly, it's trying to load my scripted lookup using inputcsv?&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 00:26:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342421#M5318</guid>
      <dc:creator>cygnetix</dc:creator>
      <dc:date>2017-03-08T00:26:24Z</dc:date>
    </item>
    <item>
      <title>Re: Using inputlookup with external_cmd</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342422#M5319</link>
      <description>&lt;P&gt;If you really want to do it in SPL then I would suggest a custom search command. I don't think you are going to get inputlookup to work since is likely requiring arguments to lookup on.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/Search/Writeasearchcommand"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.2/Search/Writeasearchcommand&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 00:53:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342422#M5319</guid>
      <dc:creator>starcher</dc:creator>
      <dc:date>2017-03-08T00:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Using inputlookup with external_cmd</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342423#M5320</link>
      <description>&lt;P&gt;I converted my script to work as a search command not long after posting the question. I agree that it looks like a search command or modular input are the way to go, but I believe that Splunk should update their documentation for inputlookup if it's not possible to use scripted lookups with this command (as the documentation currently states).&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 01:05:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342423#M5320</guid>
      <dc:creator>cygnetix</dc:creator>
      <dc:date>2017-03-08T01:05:38Z</dc:date>
    </item>
    <item>
      <title>Re: Using inputlookup with external_cmd</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342424#M5321</link>
      <description>&lt;P&gt;I've send a comment on the documentation page for inputlookup to query whether the statement that inputlookup will work with scripted lookups is correct or not. I suspect it is incorrect.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 02:13:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342424#M5321</guid>
      <dc:creator>cygnetix</dc:creator>
      <dc:date>2017-03-08T02:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: Using inputlookup with external_cmd</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342425#M5322</link>
      <description>&lt;P&gt;Yup the docs feedback is the best way to get Splunk to update the docs. The docs team watches it carefully.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 13:25:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/342425#M5322</guid>
      <dc:creator>starcher</dc:creator>
      <dc:date>2017-03-08T13:25:52Z</dc:date>
    </item>
    <item>
      <title>Re: Using inputlookup with external_cmd</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/666538#M11226</link>
      <description>&lt;P&gt;When running&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="ruby"&gt;| inputlookup testlookup&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(which is an external lookup) I get the error message:&lt;/P&gt;&lt;BLOCKQUOTE&gt;The lookup table 'testlookup' requires a .csv or KV store lookup definition&lt;/BLOCKQUOTE&gt;&lt;P&gt;... so I assume this isn't an intended use case.&lt;/P&gt;&lt;P&gt;Quite a bummer because (as per some of my earlier posts) custom search commands kind of suck.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2023 14:13:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Using-inputlookup-with-external-cmd/m-p/666538#M11226</guid>
      <dc:creator>spunk_enthusias</dc:creator>
      <dc:date>2023-10-27T14:13:57Z</dc:date>
    </item>
  </channel>
</rss>

