<?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: Where are TCP and UDP inputs indexed? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9658#M131</link>
    <description>&lt;P&gt;Since that is the sad case, then you must edit inputs.conf where the network input is defined and add the "index=foo" parameter to the input stanza.&lt;/P&gt;</description>
    <pubDate>Sat, 06 Feb 2010 06:21:39 GMT</pubDate>
    <dc:creator>hulahoop</dc:creator>
    <dc:date>2010-02-06T06:21:39Z</dc:date>
    <item>
      <title>Where are TCP and UDP inputs indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9655#M128</link>
      <description>&lt;P&gt;When I configure network inputs (TCP or UDP), I provide the port number and sourcetype, but there is nowhere to specify the index.  Where are these inputs indexed?  Can I change the index that is used for network inputs?&lt;/P&gt;</description>
      <pubDate>Sat, 06 Feb 2010 05:38:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9655#M128</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2010-02-06T05:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: Where are TCP and UDP inputs indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9656#M129</link>
      <description>&lt;P&gt;Unless otherwise specified, all data goes into the &lt;CODE&gt;default&lt;/CODE&gt; index.&lt;/P&gt;

&lt;P&gt;If adding network input through CLI, you can specify index with the &lt;CODE&gt;-index&lt;/CODE&gt; option.  (Issue &lt;CODE&gt;splunk help add&lt;/CODE&gt; for syntax help.)&lt;/P&gt;

&lt;P&gt;If adding network input through &lt;EM&gt;Manager » Data inputs » TCP » Add New&lt;/EM&gt; or &lt;EM&gt;Manager » Data inputs » UDP » Add New&lt;/EM&gt;, you should see an &lt;CODE&gt;Index&lt;/CODE&gt; dropdown list.  Is it there?  What version are you using, please?&lt;/P&gt;</description>
      <pubDate>Sat, 06 Feb 2010 05:52:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9656#M129</guid>
      <dc:creator>V_at_Splunk</dc:creator>
      <dc:date>2010-02-06T05:52:14Z</dc:date>
    </item>
    <item>
      <title>Re: Where are TCP and UDP inputs indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9657#M130</link>
      <description>&lt;P&gt;version 4.0.9, build 74233&lt;/P&gt;

&lt;P&gt;But there is no Index dropdown list in the web UI for either TCP or UDP inputs&lt;/P&gt;</description>
      <pubDate>Sat, 06 Feb 2010 06:01:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9657#M130</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2010-02-06T06:01:31Z</dc:date>
    </item>
    <item>
      <title>Re: Where are TCP and UDP inputs indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9658#M131</link>
      <description>&lt;P&gt;Since that is the sad case, then you must edit inputs.conf where the network input is defined and add the "index=foo" parameter to the input stanza.&lt;/P&gt;</description>
      <pubDate>Sat, 06 Feb 2010 06:21:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9658#M131</guid>
      <dc:creator>hulahoop</dc:creator>
      <dc:date>2010-02-06T06:21:39Z</dc:date>
    </item>
    <item>
      <title>Re: Where are TCP and UDP inputs indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9659#M132</link>
      <description>&lt;P&gt;In 4.0.x, you are indeed required to manually edit inputs.conf to specify an index for UDP/TCP inputs.&lt;/P&gt;

&lt;P&gt;In 4.1, we'll be exposing index, host, and source configuration for all input types within Splunk Manager. In addition you'll be able to blacklist/whitelist from the UI for monitor inputs.&lt;/P&gt;</description>
      <pubDate>Sat, 06 Feb 2010 06:37:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9659#M132</guid>
      <dc:creator>Gaurav</dc:creator>
      <dc:date>2010-02-06T06:37:34Z</dc:date>
    </item>
    <item>
      <title>Re: Where are TCP and UDP inputs indexed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9660#M133</link>
      <description>&lt;P&gt;Is there someway to setup listening to one port and have it direct logs to a specific index depending on whitelist/blacklist?  &lt;/P&gt;

&lt;P&gt;What I mean is can you setup logs to go to multiple indexes through 1 listening port (e.g. TCP 514). &lt;/P&gt;

&lt;P&gt;Brian&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jul 2010 04:26:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Where-are-TCP-and-UDP-inputs-indexed/m-p/9660#M133</guid>
      <dc:creator>balbano</dc:creator>
      <dc:date>2010-07-08T04:26:49Z</dc:date>
    </item>
  </channel>
</rss>

