<?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 Trade offs in using stdout vs. '/services/receivers/simple?' REST API input in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Trade-offs-in-using-stdout-vs-services-receivers-simple-REST-API/m-p/526955#M88879</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm looking for some insight into the trade offs (if any) in using stdout vs. the&amp;nbsp; '/services/receivers/simple?' REST API for scripted input. In particular in relation to different deployment options (such as a separate forwarder etc.)&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Oct 2020 19:07:56 GMT</pubDate>
    <dc:creator>ayuri</dc:creator>
    <dc:date>2020-10-28T19:07:56Z</dc:date>
    <item>
      <title>Trade offs in using stdout vs. '/services/receivers/simple?' REST API input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trade-offs-in-using-stdout-vs-services-receivers-simple-REST-API/m-p/526955#M88879</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm looking for some insight into the trade offs (if any) in using stdout vs. the&amp;nbsp; '/services/receivers/simple?' REST API for scripted input. In particular in relation to different deployment options (such as a separate forwarder etc.)&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Oct 2020 19:07:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trade-offs-in-using-stdout-vs-services-receivers-simple-REST-API/m-p/526955#M88879</guid>
      <dc:creator>ayuri</dc:creator>
      <dc:date>2020-10-28T19:07:56Z</dc:date>
    </item>
  </channel>
</rss>

