<?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: scripted inputs best practices? in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/scripted-inputs-best-practices/m-p/262336#M7988</link>
    <description>&lt;P&gt;What is the scripted input doing?&lt;/P&gt;</description>
    <pubDate>Mon, 28 Mar 2016 12:28:56 GMT</pubDate>
    <dc:creator>dcarmack_splunk</dc:creator>
    <dc:date>2016-03-28T12:28:56Z</dc:date>
    <item>
      <title>scripted inputs best practices?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/scripted-inputs-best-practices/m-p/262334#M7986</link>
      <description>&lt;P&gt;Are there any best practices regarding &lt;EM&gt;where&lt;/EM&gt; a scripted input should run?  Is there a benefit in using an intermediate forwarder to run really intensive scripted inputs?&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2016 23:33:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/scripted-inputs-best-practices/m-p/262334#M7986</guid>
      <dc:creator>bfaber</dc:creator>
      <dc:date>2016-03-26T23:33:43Z</dc:date>
    </item>
    <item>
      <title>Re: scripted inputs best practices?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/scripted-inputs-best-practices/m-p/262335#M7987</link>
      <description>&lt;P&gt;If the scripted input is really intensive, I would suggest it to run on Heavy forwarders. If ran on SH, it would consume user resources and if ran on Indexers, it's data would only be available on the indexer where it ran and would fail the purpose of distributed configuration.&lt;/P&gt;</description>
      <pubDate>Sun, 27 Mar 2016 17:52:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/scripted-inputs-best-practices/m-p/262335#M7987</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2016-03-27T17:52:47Z</dc:date>
    </item>
    <item>
      <title>Re: scripted inputs best practices?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/scripted-inputs-best-practices/m-p/262336#M7988</link>
      <description>&lt;P&gt;What is the scripted input doing?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Mar 2016 12:28:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/scripted-inputs-best-practices/m-p/262336#M7988</guid>
      <dc:creator>dcarmack_splunk</dc:creator>
      <dc:date>2016-03-28T12:28:56Z</dc:date>
    </item>
  </channel>
</rss>

