<?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: enabling HTTP Event Collector for docker container on splunk clustered setup in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290647#M5533</link>
    <description>&lt;P&gt;Hi @sim_tcr,&lt;/P&gt;

&lt;P&gt;If you are just integrating Docker with Splunk, have you seen our solution for collecting logs and metrics &lt;A href="https://splunkbase.splunk.com/app/3723/"&gt;https://splunkbase.splunk.com/app/3723/&lt;/A&gt;? You can find some documentation &lt;A href="https://www.outcoldsolutions.com/docs/"&gt;https://www.outcoldsolutions.com/docs/&lt;/A&gt; demos and screencasts. We have also comparison table with official Splunk Logging Driver &lt;A href="https://www.outcoldsolutions.com/docs/collectorfordocker/#comparing-with-splunk-logging-driver"&gt;https://www.outcoldsolutions.com/docs/collectorfordocker/#comparing-with-splunk-logging-driver&lt;/A&gt;  (btw, I am the original author of this driver).&lt;/P&gt;</description>
    <pubDate>Mon, 27 Nov 2017 06:01:52 GMT</pubDate>
    <dc:creator>outcoldman</dc:creator>
    <dc:date>2017-11-27T06:01:52Z</dc:date>
    <item>
      <title>enabling HTTP Event Collector for docker container on splunk clustered setup</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290642#M5528</link>
      <description>&lt;P&gt;We tested HTTP Event Collector for a docker container by starting the container with below,&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;--log-driver=splunk --log-opt splunk-token=&amp;lt;token&amp;gt; --log-opt splunk-url=https://&amp;lt;splunkserver&amp;gt;:8088 --log-opt splunk-insecureskipverify=true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Now we want to send the events to our actual splunk setup. We are on search head clustering and index clustering enabled, with a separate  shc deployer, deployment server and index master servers.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Which server we should enable the HTTP Event Collector? &lt;/LI&gt;
&lt;LI&gt;How can i specify the index where the events should be forwarded?&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2017 14:10:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290642#M5528</guid>
      <dc:creator>sim_tcr</dc:creator>
      <dc:date>2017-11-20T14:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: enabling HTTP Event Collector for docker container on splunk clustered setup</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290643#M5529</link>
      <description>&lt;P&gt;Hi @sim_tcr!&lt;/P&gt;

&lt;P&gt;The best advice for you would require a peek at your existing architecture and data volumes, but you should start by having a look at dev.splunk.com for HEC architectures:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://dev.splunk.com/view/event-collector/SP-CAAAE73"&gt;http://dev.splunk.com/view/event-collector/SP-CAAAE73&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If you are just getting started you could look at having a Heavy forwarder in place to catch the HEC traffic and pass it to your indexers, or a pool of HFs, or you could also just enable it on all your indexers - although you will want to be careful with that depending on the volume of traffic you expect. &lt;/P&gt;

&lt;P&gt;As for routing to an index, check out the docs on HEC tokens. You can set the index/sourcetype there!&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2017 15:00:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290643#M5529</guid>
      <dc:creator>mattymo</dc:creator>
      <dc:date>2017-11-20T15:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: enabling HTTP Event Collector for docker container on splunk clustered setup</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290644#M5530</link>
      <description>&lt;P&gt;Thank you for responding.&lt;BR /&gt;
I think we want to go with &lt;A href="http://dev.splunk.com/view/event-collector/SP-CAAAE73#scen1"&gt;http://dev.splunk.com/view/event-collector/SP-CAAAE73#scen1&lt;/A&gt;&lt;BR /&gt;
We are at 6.3.3 and referring &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.3/Data/UsetheHTTPEventCollector"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.3/Data/UsetheHTTPEventCollector&lt;/A&gt;&lt;BR /&gt;
when checking "select allowed indexes" field, we do not see all our indexes from the index cluster listed there.&lt;BR /&gt;
Do you know what are we missing?&lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2017 15:07:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290644#M5530</guid>
      <dc:creator>sim_tcr</dc:creator>
      <dc:date>2017-11-20T15:07:46Z</dc:date>
    </item>
    <item>
      <title>Re: enabling HTTP Event Collector for docker container on splunk clustered setup</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290645#M5531</link>
      <description>&lt;P&gt;You need to tell your HF about them in indexes.conf&lt;/P&gt;

&lt;P&gt;Grab the TA from the indexer cluster and use that indexes.conf on the HF. &lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2017 15:18:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290645#M5531</guid>
      <dc:creator>mattymo</dc:creator>
      <dc:date>2017-11-20T15:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: enabling HTTP Event Collector for docker container on splunk clustered setup</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290646#M5532</link>
      <description>&lt;P&gt;Great answer @mmodestino!&lt;/P&gt;

&lt;P&gt;@sim_tcr - Remember that if you start with Scenario 1 and you have to change/rebuilt the HEC server, you'll need to update all the clients (apps) sending data. As such, use a VIP or a Load Balancer even if pointing to that one instance. This will increase availability and failover options besides allowing for scalability later and essentially making the transition to Scenario 3 seamless.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 13:51:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290646#M5532</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2017-11-22T13:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: enabling HTTP Event Collector for docker container on splunk clustered setup</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290647#M5533</link>
      <description>&lt;P&gt;Hi @sim_tcr,&lt;/P&gt;

&lt;P&gt;If you are just integrating Docker with Splunk, have you seen our solution for collecting logs and metrics &lt;A href="https://splunkbase.splunk.com/app/3723/"&gt;https://splunkbase.splunk.com/app/3723/&lt;/A&gt;? You can find some documentation &lt;A href="https://www.outcoldsolutions.com/docs/"&gt;https://www.outcoldsolutions.com/docs/&lt;/A&gt; demos and screencasts. We have also comparison table with official Splunk Logging Driver &lt;A href="https://www.outcoldsolutions.com/docs/collectorfordocker/#comparing-with-splunk-logging-driver"&gt;https://www.outcoldsolutions.com/docs/collectorfordocker/#comparing-with-splunk-logging-driver&lt;/A&gt;  (btw, I am the original author of this driver).&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2017 06:01:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/enabling-HTTP-Event-Collector-for-docker-container-on-splunk/m-p/290647#M5533</guid>
      <dc:creator>outcoldman</dc:creator>
      <dc:date>2017-11-27T06:01:52Z</dc:date>
    </item>
  </channel>
</rss>

