<?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: Does HEC have to run on 8088?  Could it also run on 9997 port? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Does-HEC-have-to-run-on-8088-Could-it-also-run-on-9997-port/m-p/420551#M21065</link>
    <description>&lt;P&gt;As the others mention. You can change the port. However. You mention forwarder. They do not talk HEC. The talk splunk2splunk protocol. So running HEC on 9997 will not work to receive UF data. &lt;/P&gt;</description>
    <pubDate>Wed, 06 Mar 2019 01:25:19 GMT</pubDate>
    <dc:creator>starcher</dc:creator>
    <dc:date>2019-03-06T01:25:19Z</dc:date>
    <item>
      <title>Does HEC have to run on 8088?  Could it also run on 9997 port?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Does-HEC-have-to-run-on-8088-Could-it-also-run-on-9997-port/m-p/420548#M21062</link>
      <description>&lt;P&gt;We are planning to implement HEC on our Splunk setup, we are looking to see if HEC works on 9997 or should it only use 8088 port.&lt;/P&gt;

&lt;P&gt;We already have UFs using 9997 port&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2019 11:07:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Does-HEC-have-to-run-on-8088-Could-it-also-run-on-9997-port/m-p/420548#M21062</guid>
      <dc:creator>Splunker2911</dc:creator>
      <dc:date>2019-03-04T11:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: Does HEC have to run on 8088?  Could it also run on 9997 port?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Does-HEC-have-to-run-on-8088-Could-it-also-run-on-9997-port/m-p/420549#M21063</link>
      <description>&lt;P&gt;You can run HEC on any port but obviously, it cant be a port in use elsewhere on the same host.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2019 13:02:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Does-HEC-have-to-run-on-8088-Could-it-also-run-on-9997-port/m-p/420549#M21063</guid>
      <dc:creator>nickhills</dc:creator>
      <dc:date>2019-03-04T13:02:15Z</dc:date>
    </item>
    <item>
      <title>Re: Does HEC have to run on 8088?  Could it also run on 9997 port?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Does-HEC-have-to-run-on-8088-Could-it-also-run-on-9997-port/m-p/420550#M21064</link>
      <description>&lt;P&gt;You can run it on whatever port you can:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.4/Data/UsetheHTTPEventCollector#HEC_and_self-service_Splunk_Cloud"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.4/Data/UsetheHTTPEventCollector#HEC_and_self-service_Splunk_Cloud&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2019 13:10:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Does-HEC-have-to-run-on-8088-Could-it-also-run-on-9997-port/m-p/420550#M21064</guid>
      <dc:creator>tiagofbmm</dc:creator>
      <dc:date>2019-03-04T13:10:13Z</dc:date>
    </item>
    <item>
      <title>Re: Does HEC have to run on 8088?  Could it also run on 9997 port?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Does-HEC-have-to-run-on-8088-Could-it-also-run-on-9997-port/m-p/420551#M21065</link>
      <description>&lt;P&gt;As the others mention. You can change the port. However. You mention forwarder. They do not talk HEC. The talk splunk2splunk protocol. So running HEC on 9997 will not work to receive UF data. &lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2019 01:25:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Does-HEC-have-to-run-on-8088-Could-it-also-run-on-9997-port/m-p/420551#M21065</guid>
      <dc:creator>starcher</dc:creator>
      <dc:date>2019-03-06T01:25:19Z</dc:date>
    </item>
  </channel>
</rss>

