<?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: Sending data with HEC vs modular inputs vs raw port in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Sending-data-with-HEC-vs-modular-inputs-vs-raw-port/m-p/458552#M79245</link>
    <description>&lt;P&gt;Don't use network ports. you get no load balancing etc. HEC is HTTP post (web hook) meant to be web load balanced. Modular inputs usually you run on a heavy forwarder so you have to plan to have a backup of all inputs etc in case the box dies and you have to rebuild it.&lt;/P&gt;</description>
    <pubDate>Wed, 10 Jul 2019 13:00:59 GMT</pubDate>
    <dc:creator>starcher</dc:creator>
    <dc:date>2019-07-10T13:00:59Z</dc:date>
    <item>
      <title>Sending data with HEC vs modular inputs vs raw port</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sending-data-with-HEC-vs-modular-inputs-vs-raw-port/m-p/458551#M79244</link>
      <description>&lt;P&gt;I'm trying to figure out the pros and cons of using each of these methods to send data to Splunk. Let's assume I have full control over the data, so I can send it in any format.&lt;/P&gt;

&lt;P&gt;To the best of my understanding:&lt;BR /&gt;
HEC: push data to Spunk via Splunk's REST API&lt;BR /&gt;
Modular input: a script (?) that runs on the Splunk side, good for pulling data from external REST APIs&lt;BR /&gt;
Open port: (&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.0/Data/Monitornetworkports"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.0/Data/Monitornetworkports&lt;/A&gt;) send arbitrary data over a raw port for Splunk to index, and the indexing can be configured on the Splunk end&lt;/P&gt;

&lt;P&gt;What other considerations should I be keeping in mind when deciding between these approaches? Any limitations to be aware of?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jul 2019 19:56:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sending-data-with-HEC-vs-modular-inputs-vs-raw-port/m-p/458551#M79244</guid>
      <dc:creator>yvonnec</dc:creator>
      <dc:date>2019-07-09T19:56:11Z</dc:date>
    </item>
    <item>
      <title>Re: Sending data with HEC vs modular inputs vs raw port</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sending-data-with-HEC-vs-modular-inputs-vs-raw-port/m-p/458552#M79245</link>
      <description>&lt;P&gt;Don't use network ports. you get no load balancing etc. HEC is HTTP post (web hook) meant to be web load balanced. Modular inputs usually you run on a heavy forwarder so you have to plan to have a backup of all inputs etc in case the box dies and you have to rebuild it.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jul 2019 13:00:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sending-data-with-HEC-vs-modular-inputs-vs-raw-port/m-p/458552#M79245</guid>
      <dc:creator>starcher</dc:creator>
      <dc:date>2019-07-10T13:00:59Z</dc:date>
    </item>
    <item>
      <title>Re: Sending data with HEC vs modular inputs vs raw port</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sending-data-with-HEC-vs-modular-inputs-vs-raw-port/m-p/458553#M79246</link>
      <description>&lt;P&gt;Thank you, this is helpful!&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jul 2019 14:21:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sending-data-with-HEC-vs-modular-inputs-vs-raw-port/m-p/458553#M79246</guid>
      <dc:creator>yvonnec</dc:creator>
      <dc:date>2019-07-10T14:21:03Z</dc:date>
    </item>
  </channel>
</rss>

