<?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: Why is scripted input not forwarding to peers ? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-scripted-input-not-forwarding-to-peers/m-p/190341#M37909</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;
If there is no need/requirement for local indexing, it can be disabled:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Go to Splunk install directory
cd bin
./splunk disable local-index
./splunk restart 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You can explicitly define your data inputs in your inputs and outputs.conf. Assuming it's a Linux env and you are using default ports..Eg:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;inputs.conf  
[script:///Path to your script]
disabled = false
interval = your_interval (cron or secs)
sourcetype = your_sourcetype
index = your_index_on_cluster

outputs.conf
[indexAndForward]
index = false

[tcpout]
defaultGroup = your-group

[tcpout:your-group]
server=idx1:9997,idx2:9997,idx3:9997
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 19 May 2015 13:41:53 GMT</pubDate>
    <dc:creator>Yasaswy</dc:creator>
    <dc:date>2015-05-19T13:41:53Z</dc:date>
    <item>
      <title>Why is scripted input not forwarding to peers ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-scripted-input-not-forwarding-to-peers/m-p/190340#M37908</link>
      <description>&lt;P&gt;Our setup comprises of 1 heavy forwarder, 3 searchheads and 3 peers/indexers all in the clustered environment. &lt;BR /&gt;
We are trying to create a scripted input on the heavy forwarder. We need the scripted input to output the data on an index on the peered cluster. When we try to create the scripted input on the heavy forwarder via the UI only the local indexes on the heavy forwarder show up. &lt;/P&gt;

&lt;P&gt;How can we achieve our main objective without storing data on the heavy forwarder and only storing it in on the indexers.&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2015 00:05:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-scripted-input-not-forwarding-to-peers/m-p/190340#M37908</guid>
      <dc:creator>tdiestel</dc:creator>
      <dc:date>2015-05-19T00:05:52Z</dc:date>
    </item>
    <item>
      <title>Re: Why is scripted input not forwarding to peers ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-scripted-input-not-forwarding-to-peers/m-p/190341#M37909</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
If there is no need/requirement for local indexing, it can be disabled:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Go to Splunk install directory
cd bin
./splunk disable local-index
./splunk restart 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You can explicitly define your data inputs in your inputs and outputs.conf. Assuming it's a Linux env and you are using default ports..Eg:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;inputs.conf  
[script:///Path to your script]
disabled = false
interval = your_interval (cron or secs)
sourcetype = your_sourcetype
index = your_index_on_cluster

outputs.conf
[indexAndForward]
index = false

[tcpout]
defaultGroup = your-group

[tcpout:your-group]
server=idx1:9997,idx2:9997,idx3:9997
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 19 May 2015 13:41:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-scripted-input-not-forwarding-to-peers/m-p/190341#M37909</guid>
      <dc:creator>Yasaswy</dc:creator>
      <dc:date>2015-05-19T13:41:53Z</dc:date>
    </item>
  </channel>
</rss>

