<?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: New and started to input data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/New-and-started-to-input-data/m-p/228253#M98974</link>
    <description>&lt;P&gt;Splunk does not care what port you want to monitor - it can be anything. However, Splunk may be restricted because you are running Splunk from a non-privileged account (as you should).&lt;/P&gt;

&lt;P&gt;On Linux for example, ports under 1024 are considered privileged; a non- root user cannot read these ports. This may be why you can't monitor port 80. There are ways to get around this.&lt;/P&gt;

&lt;P&gt;I am also concerned when you say "monitor port 80 for traffic." Splunk's network inputs (TCP and UDP) read data from the port and index it; is this what you mean by "monitoring"? I feel like this is not what you want. You might also want to look at the free &lt;A href="http://splunkbase.splunk.com/app/1809/"&gt;Splunk App for Stream&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 13 Aug 2016 05:06:25 GMT</pubDate>
    <dc:creator>lguinn2</dc:creator>
    <dc:date>2016-08-13T05:06:25Z</dc:date>
    <item>
      <title>New and started to input data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/New-and-started-to-input-data/m-p/228252#M98973</link>
      <description>&lt;P&gt;So this is the first time I was trying to input the TCP data port to my monitoring.  I am behind a NAT as it is with a FioS router in a home network environment.  I wanted to monitor port 80 for web but that is not being allowed (I presume it has to do with the NAT).  How do I monitor my computer as a test for traffic going/coming from the web on the Splunk monitoring tool?  What settings/port numbers do I need as the input data?&lt;/P&gt;</description>
      <pubDate>Fri, 12 Aug 2016 23:38:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/New-and-started-to-input-data/m-p/228252#M98973</guid>
      <dc:creator>dxw350</dc:creator>
      <dc:date>2016-08-12T23:38:39Z</dc:date>
    </item>
    <item>
      <title>Re: New and started to input data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/New-and-started-to-input-data/m-p/228253#M98974</link>
      <description>&lt;P&gt;Splunk does not care what port you want to monitor - it can be anything. However, Splunk may be restricted because you are running Splunk from a non-privileged account (as you should).&lt;/P&gt;

&lt;P&gt;On Linux for example, ports under 1024 are considered privileged; a non- root user cannot read these ports. This may be why you can't monitor port 80. There are ways to get around this.&lt;/P&gt;

&lt;P&gt;I am also concerned when you say "monitor port 80 for traffic." Splunk's network inputs (TCP and UDP) read data from the port and index it; is this what you mean by "monitoring"? I feel like this is not what you want. You might also want to look at the free &lt;A href="http://splunkbase.splunk.com/app/1809/"&gt;Splunk App for Stream&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Aug 2016 05:06:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/New-and-started-to-input-data/m-p/228253#M98974</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2016-08-13T05:06:25Z</dc:date>
    </item>
  </channel>
</rss>

