<?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: What uses the management port? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9315#M50</link>
    <description>&lt;P&gt;The management port is used by all things that need to communicate TO the splunkd, excepting forwarders.  &lt;/P&gt;

&lt;P&gt;Essentially the management port is a request-response model communication path, implemented as REST over HTTP (historically SOAP was used in older products).   Thus anything that is a request with a result occurs over the management port.  Forwarding is a continuous stream and has its own protocol.&lt;/P&gt;

&lt;P&gt;Things that will have to access the httpd.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;the Splunk command line for most commands&lt;/LI&gt;
&lt;LI&gt;SplunkWeb&lt;/LI&gt;
&lt;LI&gt;distributed search&lt;/LI&gt;
&lt;LI&gt;The summary backfill script (which invokes the splunk commandline)&lt;/LI&gt;
&lt;LI&gt;any REST clients of your own creation&lt;/LI&gt;
&lt;LI&gt;In splunk 3.x, the scheduled search launcher&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Wed, 20 Jan 2010 07:34:32 GMT</pubDate>
    <dc:creator>jrodman</dc:creator>
    <dc:date>2010-01-20T07:34:32Z</dc:date>
    <item>
      <title>What uses the management port?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9313#M48</link>
      <description>&lt;P&gt;Under what circumstances does the splunkd service need to be accesable by anyone/thing besides the http server?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2010 04:12:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9313#M48</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2010-01-20T04:12:02Z</dc:date>
    </item>
    <item>
      <title>Re: What uses the management port?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9314#M49</link>
      <description>&lt;P&gt;Unless I'm sorely mistaken, CLI communicates with &lt;CODE&gt;splunkd&lt;/CODE&gt; via the mgmt port.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2010 04:45:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9314#M49</guid>
      <dc:creator>V_at_Splunk</dc:creator>
      <dc:date>2010-01-20T04:45:24Z</dc:date>
    </item>
    <item>
      <title>Re: What uses the management port?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9315#M50</link>
      <description>&lt;P&gt;The management port is used by all things that need to communicate TO the splunkd, excepting forwarders.  &lt;/P&gt;

&lt;P&gt;Essentially the management port is a request-response model communication path, implemented as REST over HTTP (historically SOAP was used in older products).   Thus anything that is a request with a result occurs over the management port.  Forwarding is a continuous stream and has its own protocol.&lt;/P&gt;

&lt;P&gt;Things that will have to access the httpd.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;the Splunk command line for most commands&lt;/LI&gt;
&lt;LI&gt;SplunkWeb&lt;/LI&gt;
&lt;LI&gt;distributed search&lt;/LI&gt;
&lt;LI&gt;The summary backfill script (which invokes the splunk commandline)&lt;/LI&gt;
&lt;LI&gt;any REST clients of your own creation&lt;/LI&gt;
&lt;LI&gt;In splunk 3.x, the scheduled search launcher&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Wed, 20 Jan 2010 07:34:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9315#M50</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2010-01-20T07:34:32Z</dc:date>
    </item>
    <item>
      <title>Re: What uses the management port?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9316#M51</link>
      <description>&lt;P&gt;yes, the CLI communicates with splunkd via the management port.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2010 07:36:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9316#M51</guid>
      <dc:creator>benstraw</dc:creator>
      <dc:date>2010-01-20T07:36:17Z</dc:date>
    </item>
    <item>
      <title>Re: What uses the management port?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9317#M52</link>
      <description>&lt;P&gt;Used by deployment clients as well. This is is specified in deploymentclient.conf with attribute 'targetUri'.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Jan 2010 02:35:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9317#M52</guid>
      <dc:creator>Jag</dc:creator>
      <dc:date>2010-01-23T02:35:14Z</dc:date>
    </item>
    <item>
      <title>Re: What uses the management port?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9318#M53</link>
      <description>&lt;P&gt;management port is required for internal communication primarily between the splunk instances in short &lt;BR /&gt;
We can change this if we require by editing the configuration files.&lt;BR /&gt;
several other ports are 8000 web port 9997 - incoming port 8080 - replication port&lt;/P&gt;</description>
      <pubDate>Thu, 08 Mar 2018 11:55:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-uses-the-management-port/m-p/9318#M53</guid>
      <dc:creator>arunsundaram</dc:creator>
      <dc:date>2018-03-08T11:55:29Z</dc:date>
    </item>
  </channel>
</rss>

