<?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 Using a .csv as part of a search in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Using-a-csv-as-part-of-a-search/m-p/336184#M62144</link>
    <description>&lt;P&gt;New splunk user, trying to get my feet under me. here's the situation;&lt;/P&gt;

&lt;P&gt;We have a rather large splunk deployment, and my group often does searches using phone number (TN). Some of our searches involve a &lt;EM&gt;lot&lt;/EM&gt; of numbers, so the search is basically "WTN=0000000000 OR WTN=1111111111 OR..." repeated about a thousand times (not exaggerating, BTW). I've been told that it's easier and faster to use a lookup table instead, but all the reading on lookup tables I've found seem to indicate that adding the .csv makes it more or less a permanent addition to the splunk data, not to mention that the whole process seems kinda convoluted for a simple (and often one-time) search.&lt;/P&gt;

&lt;P&gt;Basically, what I'd like to do is be able to say "search index x for the TNs in this .csv, and return these fields" more or less on the fly, without adding a lot of data to splunk that will most likely never be used again. Is there an easy way to do this? Thanks!&lt;/P&gt;</description>
    <pubDate>Sat, 04 Mar 2017 23:22:46 GMT</pubDate>
    <dc:creator>cpressl</dc:creator>
    <dc:date>2017-03-04T23:22:46Z</dc:date>
    <item>
      <title>Using a .csv as part of a search</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-a-csv-as-part-of-a-search/m-p/336184#M62144</link>
      <description>&lt;P&gt;New splunk user, trying to get my feet under me. here's the situation;&lt;/P&gt;

&lt;P&gt;We have a rather large splunk deployment, and my group often does searches using phone number (TN). Some of our searches involve a &lt;EM&gt;lot&lt;/EM&gt; of numbers, so the search is basically "WTN=0000000000 OR WTN=1111111111 OR..." repeated about a thousand times (not exaggerating, BTW). I've been told that it's easier and faster to use a lookup table instead, but all the reading on lookup tables I've found seem to indicate that adding the .csv makes it more or less a permanent addition to the splunk data, not to mention that the whole process seems kinda convoluted for a simple (and often one-time) search.&lt;/P&gt;

&lt;P&gt;Basically, what I'd like to do is be able to say "search index x for the TNs in this .csv, and return these fields" more or less on the fly, without adding a lot of data to splunk that will most likely never be used again. Is there an easy way to do this? Thanks!&lt;/P&gt;</description>
      <pubDate>Sat, 04 Mar 2017 23:22:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-a-csv-as-part-of-a-search/m-p/336184#M62144</guid>
      <dc:creator>cpressl</dc:creator>
      <dc:date>2017-03-04T23:22:46Z</dc:date>
    </item>
    <item>
      <title>Re: Using a .csv as part of a search</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-a-csv-as-part-of-a-search/m-p/336185#M62145</link>
      <description>&lt;P&gt;Let's assume that you have a lookup file called &lt;CODE&gt;WTN.csv&lt;/CODE&gt; which has a header line that says only &lt;CODE&gt;WTN&lt;/CODE&gt;.  You can skip all &lt;CODE&gt;WTNs&lt;/CODE&gt; in the file like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Your Search Here NOT [|inputscsv WTN.csv]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sun, 05 Mar 2017 09:15:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-a-csv-as-part-of-a-search/m-p/336185#M62145</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-03-05T09:15:51Z</dc:date>
    </item>
  </channel>
</rss>

