<?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: trigger a script on a Forwarder from Indexer on another host? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/trigger-a-script-on-a-Forwarder-from-Indexer-on-another-host/m-p/36262#M6620</link>
    <description>&lt;P&gt;Thanks, that's a good idea given my restrictions.  I have a common NAS share that should serve as a means of communication between the two pieces, and I'm already thinking of other uses for "conditional scripts".&lt;/P&gt;</description>
    <pubDate>Wed, 02 Feb 2011 02:54:32 GMT</pubDate>
    <dc:creator>jhedgpeth</dc:creator>
    <dc:date>2011-02-02T02:54:32Z</dc:date>
    <item>
      <title>trigger a script on a Forwarder from Indexer on another host?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/trigger-a-script-on-a-Forwarder-from-Indexer-on-another-host/m-p/36260#M6618</link>
      <description>&lt;P&gt;I've got a single v4 Splunk Indexer/Search.  Feeding it are multiple Forwarders that have local indexing disabled and have all their inputs/conf deployed to them in apps.  I'd like for a scheduled search on the Indexer to be able to trigger a script I've deployed on the forwarder.&lt;/P&gt;

&lt;P&gt;My limitations are that I don't want the script to run and send data continuously (which would be easy) because 99% of the time it's not relevant, and we're trying to isolate a problem that occurs sporadically.  Also, our environment doesn't allow password-less (automated) logins from host-to-host, so the simple ssh solution isn't available.&lt;/P&gt;

&lt;P&gt;There's doesn't appear to be anything about this in help/answers, but I may be searching for the wrong thing.  Can Splunk do this?  Am I going about this the wrong way?  Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Feb 2011 06:04:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/trigger-a-script-on-a-Forwarder-from-Indexer-on-another-host/m-p/36260#M6618</guid>
      <dc:creator>jhedgpeth</dc:creator>
      <dc:date>2011-02-01T06:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: trigger a script on a Forwarder from Indexer on another host?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/trigger-a-script-on-a-Forwarder-from-Indexer-on-another-host/m-p/36261#M6619</link>
      <description>&lt;P&gt;Hm, Splunk is not generally designed to have such a channel.&lt;/P&gt;

&lt;P&gt;You could perhaps abuse the distributed search functionality to cause a distributed search to trigger a 'command' implemented by a script, which actually updates a log which the nodes monitor.  Or something like that.  It's almost certainly more work than you'd want, and quite rube-goldberg.&lt;/P&gt;

&lt;P&gt;Personally I'd have the input scripts hit a url and if they get a successful response of say, an integer, and that integer is updated, produce the output.  Then you can fairly easily update such a number on an http of your choosing or by modifying a static asset in a splunkweb directory.&lt;/P&gt;

&lt;P&gt;Ie, personally I'd make the trigger mechanism be external to Splunk.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Feb 2011 07:36:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/trigger-a-script-on-a-Forwarder-from-Indexer-on-another-host/m-p/36261#M6619</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2011-02-01T07:36:47Z</dc:date>
    </item>
    <item>
      <title>Re: trigger a script on a Forwarder from Indexer on another host?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/trigger-a-script-on-a-Forwarder-from-Indexer-on-another-host/m-p/36262#M6620</link>
      <description>&lt;P&gt;Thanks, that's a good idea given my restrictions.  I have a common NAS share that should serve as a means of communication between the two pieces, and I'm already thinking of other uses for "conditional scripts".&lt;/P&gt;</description>
      <pubDate>Wed, 02 Feb 2011 02:54:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/trigger-a-script-on-a-Forwarder-from-Indexer-on-another-host/m-p/36262#M6620</guid>
      <dc:creator>jhedgpeth</dc:creator>
      <dc:date>2011-02-02T02:54:32Z</dc:date>
    </item>
  </channel>
</rss>

