<?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: Issue getting data in in Security</title>
    <link>https://community.splunk.com/t5/Security/Issue-getting-data-in/m-p/181351#M5397</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;To add an input by directly editing inputs.conf, add a stanza for the input. You can add the stanza to the inputs.conf file in $SPLUNK_HOME/etc/system/local/, or in your own custom application directory (in $SPLUNK_HOME/etc/apps//local). If you have not worked with Splunk's configuration files before, read "About configuration files" before you begin.&lt;/P&gt;

&lt;P&gt;You configure the data input by adding attribute/value pairs to its stanza. You can set multiple attributes in an input stanza. If you do not specify a value for an attribute, Splunk Enterprise uses the default value that's preset in $SPLUNK_HOME/etc/system/default/inputs.conf.&lt;/P&gt;

&lt;P&gt;Here's a simple example of adding a network input. This configuration directs Splunk Enterprise to listen on TCP port 9995 for raw data from any remote server. The host of the data is set as the DNS name of the remote server. All data will also be assigned the source type "log4j" and the source "tcp:9995".&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcp://:9995]
connection_host = dns
sourcetype = log4j
source = tcp:9995
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;For more information, visit:&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.5/Indexer/Aboutindexesandindexers" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.5/Indexer/Aboutindexesandindexers&lt;/A&gt; &lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 18:37:07 GMT</pubDate>
    <dc:creator>Patient</dc:creator>
    <dc:date>2020-09-28T18:37:07Z</dc:date>
    <item>
      <title>Issue getting data in</title>
      <link>https://community.splunk.com/t5/Security/Issue-getting-data-in/m-p/181349#M5395</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have an issue when i try to get data in Splunk 6.2.1&lt;BR /&gt;
I created /opt/splunk/system/local/inputs.conf  but i receive no data.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp://@ip:514]
connection_host = ip
index = firewall
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;whereas when iadd data from the webUI, there are no issue.&lt;BR /&gt;
I put only udp://514, i know this is not a connectivity problem.&lt;BR /&gt;
None of my modifications in the config file are apply when i restart Splunk&lt;/P&gt;

&lt;P&gt;I really need help on this.&lt;/P&gt;

&lt;P&gt;Thank you &lt;/P&gt;</description>
      <pubDate>Mon, 12 Jan 2015 11:00:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Issue-getting-data-in/m-p/181349#M5395</guid>
      <dc:creator>ThomasLeroy</dc:creator>
      <dc:date>2015-01-12T11:00:18Z</dc:date>
    </item>
    <item>
      <title>Re: Issue getting data in</title>
      <link>https://community.splunk.com/t5/Security/Issue-getting-data-in/m-p/181350#M5396</link>
      <description>&lt;P&gt;Hi ThomasLeroy,&lt;/P&gt;

&lt;P&gt;adding an IP to this stanza, will not bind UDP input to this IP, but only accept traffic from this IP. &lt;BR /&gt;
See the docs for more details on this &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/admin/inputsconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/admin/inputsconf&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp://&amp;lt;remote server&amp;gt;:&amp;lt;port&amp;gt;]
* If &amp;lt;remote server&amp;gt; is specified, the specified port will only accept data from that server.
* If &amp;lt;remote server&amp;gt; is empty - [udp://&amp;lt;port&amp;gt;] - the port will accept data sent from any server.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jan 2015 12:30:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Issue-getting-data-in/m-p/181350#M5396</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-01-12T12:30:56Z</dc:date>
    </item>
    <item>
      <title>Re: Issue getting data in</title>
      <link>https://community.splunk.com/t5/Security/Issue-getting-data-in/m-p/181351#M5397</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;To add an input by directly editing inputs.conf, add a stanza for the input. You can add the stanza to the inputs.conf file in $SPLUNK_HOME/etc/system/local/, or in your own custom application directory (in $SPLUNK_HOME/etc/apps//local). If you have not worked with Splunk's configuration files before, read "About configuration files" before you begin.&lt;/P&gt;

&lt;P&gt;You configure the data input by adding attribute/value pairs to its stanza. You can set multiple attributes in an input stanza. If you do not specify a value for an attribute, Splunk Enterprise uses the default value that's preset in $SPLUNK_HOME/etc/system/default/inputs.conf.&lt;/P&gt;

&lt;P&gt;Here's a simple example of adding a network input. This configuration directs Splunk Enterprise to listen on TCP port 9995 for raw data from any remote server. The host of the data is set as the DNS name of the remote server. All data will also be assigned the source type "log4j" and the source "tcp:9995".&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcp://:9995]
connection_host = dns
sourcetype = log4j
source = tcp:9995
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;For more information, visit:&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.5/Indexer/Aboutindexesandindexers" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.5/Indexer/Aboutindexesandindexers&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 18:37:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Issue-getting-data-in/m-p/181351#M5397</guid>
      <dc:creator>Patient</dc:creator>
      <dc:date>2020-09-28T18:37:07Z</dc:date>
    </item>
  </channel>
</rss>

