<?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 Saving alert triggerred scripts inside apps in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9798#M10</link>
    <description>&lt;P&gt;I want to configure a saved search alert to trigger a script contained inside my app. The security measures only allow me to run the script from $SPLUNK_HOME/bin/scripts, making it difficult to ship it with the app.&lt;/P&gt;

&lt;P&gt;Is there a workaround for this?&lt;/P&gt;</description>
    <pubDate>Thu, 18 Feb 2010 08:13:02 GMT</pubDate>
    <dc:creator>Leo</dc:creator>
    <dc:date>2010-02-18T08:13:02Z</dc:date>
    <item>
      <title>Saving alert triggerred scripts inside apps</title>
      <link>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9798#M10</link>
      <description>&lt;P&gt;I want to configure a saved search alert to trigger a script contained inside my app. The security measures only allow me to run the script from $SPLUNK_HOME/bin/scripts, making it difficult to ship it with the app.&lt;/P&gt;

&lt;P&gt;Is there a workaround for this?&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2010 08:13:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9798#M10</guid>
      <dc:creator>Leo</dc:creator>
      <dc:date>2010-02-18T08:13:02Z</dc:date>
    </item>
    <item>
      <title>Re: Saving alert triggerred scripts inside apps</title>
      <link>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9799#M11</link>
      <description>&lt;P&gt;The solution would be to put the script inside /etc/apps/[appname]/bin 
and put the script name in savedsearches.conf:&lt;/P&gt;

&lt;P&gt;action.script.filename = myscript.bat&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2010 08:18:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9799#M11</guid>
      <dc:creator>Leo</dc:creator>
      <dc:date>2010-02-18T08:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: Saving alert triggerred scripts inside apps</title>
      <link>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9800#M12</link>
      <description>&lt;P&gt;The script should actually be placed directly in /etc/apps/[appname]/bin. Files in a 'script' subdirectory of 'bin' are probably ignored.&lt;/P&gt;</description>
      <pubDate>Tue, 18 May 2010 07:24:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9800#M12</guid>
      <dc:creator>ewoo</dc:creator>
      <dc:date>2010-05-18T07:24:25Z</dc:date>
    </item>
    <item>
      <title>Re: Saving alert triggerred scripts inside apps</title>
      <link>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9801#M13</link>
      <description>&lt;P&gt;Leo, this doesn't appear to work, at least in version 4.1.2.  When I create a script (verified executable) in $SPLUNK_HOME/etc/apps/myapp/bin/ and create a scheduled search (also running out of myapps/local/savedsearch.conf)  that triggers the script, I still see that Splunk is looking in $SPLUNK_HOME/bin/scripts for the script:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ERROR script - Cannot find script at /home/support/splunk/bin/scripts/myscript.sh
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What am I missing to get it to run from my app's bin directory?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jun 2010 01:09:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9801#M13</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2010-06-10T01:09:40Z</dc:date>
    </item>
    <item>
      <title>Re: Saving alert triggerred scripts inside apps</title>
      <link>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9802#M14</link>
      <description>&lt;P&gt;Actually I'm trying this now on 4.1.3 and it doesn't work when the script is placed in either script or bin directory.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jun 2010 02:08:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9802#M14</guid>
      <dc:creator>Leo</dc:creator>
      <dc:date>2010-06-10T02:08:30Z</dc:date>
    </item>
    <item>
      <title>Re: Saving alert triggerred scripts inside apps</title>
      <link>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9803#M15</link>
      <description>&lt;P&gt;the alert script should be placed in:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;$SPLUNK_HOME/etc/apps/&amp;lt;app&amp;gt;/bin/scripts/
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The error message you're seeing occurs because splunk first looks in the above app level directory and then falls back to the system level script location &lt;CODE&gt;$SPLUNK_HOME/bin/scripts/&lt;/CODE&gt; - if a script is not found at the system level a failure is reported and the system level dir is output.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jun 2010 04:44:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Saving-alert-triggerred-scripts-inside-apps/m-p/9803#M15</guid>
      <dc:creator>Ledion_Bitincka</dc:creator>
      <dc:date>2010-06-10T04:44:13Z</dc:date>
    </item>
  </channel>
</rss>

