<?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 Splunk HEC using distributed deployment in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-HEC-using-distributed-deployment/m-p/430587#M15265</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I am aiming to enable HEC on my current indexers (in cluster) and I would like to use a deployment-server to manage the tokens.&lt;/P&gt;

&lt;P&gt;I already have a deployment-server for the Universal forwarders configuration.&lt;/P&gt;

&lt;P&gt;Can someone please help confirming that I can leverage the same deployment-server for both UF and HEC ?&lt;/P&gt;

&lt;P&gt;Thanks for your help.&lt;/P&gt;

&lt;P&gt;Cyril&lt;/P&gt;</description>
    <pubDate>Wed, 24 Apr 2019 14:13:41 GMT</pubDate>
    <dc:creator>SirHill17</dc:creator>
    <dc:date>2019-04-24T14:13:41Z</dc:date>
    <item>
      <title>Splunk HEC using distributed deployment</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-HEC-using-distributed-deployment/m-p/430587#M15265</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I am aiming to enable HEC on my current indexers (in cluster) and I would like to use a deployment-server to manage the tokens.&lt;/P&gt;

&lt;P&gt;I already have a deployment-server for the Universal forwarders configuration.&lt;/P&gt;

&lt;P&gt;Can someone please help confirming that I can leverage the same deployment-server for both UF and HEC ?&lt;/P&gt;

&lt;P&gt;Thanks for your help.&lt;/P&gt;

&lt;P&gt;Cyril&lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2019 14:13:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-HEC-using-distributed-deployment/m-p/430587#M15265</guid>
      <dc:creator>SirHill17</dc:creator>
      <dc:date>2019-04-24T14:13:41Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk HEC using distributed deployment</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-HEC-using-distributed-deployment/m-p/430588#M15266</link>
      <description>&lt;P&gt;Instead of Deployment Server, I'll prefer Cluster Master to handle HEC configuration and tokens on all Splunk Indexers in Cluster (As far as I remember only pain point is when you'll push bundle from CM to Indexers for new HEC token(s), it will restart Splunk process on Indexers)&lt;/P&gt;

&lt;P&gt;Have a look at &lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.6/Data/ScaleHTTPEventCollector#Place_and_distribute_the_HEC_on_indexer_cluster_peer_nodes"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.6/Data/ScaleHTTPEventCollector#Place_and_distribute_the_HEC_on_indexer_cluster_peer_nodes&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2019 14:30:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-HEC-using-distributed-deployment/m-p/430588#M15266</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2019-04-24T14:30:46Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk HEC using distributed deployment</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-HEC-using-distributed-deployment/m-p/430589#M15267</link>
      <description>&lt;P&gt;Thanks for your inputs. I didn't think about this solution. The point about restart Splunk process is the same with Deployment-Server. But it makes more sense now to me to leverage the Cluster Manager than the Deployment-Server used for UF.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2019 12:27:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-HEC-using-distributed-deployment/m-p/430589#M15267</guid>
      <dc:creator>SirHill17</dc:creator>
      <dc:date>2019-04-26T12:27:31Z</dc:date>
    </item>
  </channel>
</rss>

