<?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: Script Alert Argument? in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66709#M923</link>
    <description>&lt;P&gt;It looks like there may be a way to do it but you'll have to make some modifications to config files and scripts.  I would recommend backing up any files first of course so you can roll back.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/32385/alert-script-and-severity"&gt;http://splunk-base.splunk.com/answers/32385/alert-script-and-severity&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 30 Apr 2012 21:54:31 GMT</pubDate>
    <dc:creator>sdaniels</dc:creator>
    <dc:date>2012-04-30T21:54:31Z</dc:date>
    <item>
      <title>Script Alert Argument?</title>
      <link>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66707#M921</link>
      <description>&lt;P&gt;Hi~All&lt;/P&gt;

&lt;P&gt;Does Splunk support only and just 8 argument to pass to alert script? Can I customize these arguments which is generated from search result and pass it to alert script? By the way, does script alert support javascript? &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;$0 = Script name
$1 = Number of events returned
$2 = Search terms
$3 = Fully qualified query string
$4 = Name of saved search
$5 = Trigger reason (i.e. "The number of events was greater than 1")
$6 = Browser URL to view the saved search
$7 = This option has been deprecated and is no longer used
$8 = File where the results for this search are stored (contains raw results) 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;thanks in advance!!&lt;/P&gt;</description>
      <pubDate>Tue, 30 Aug 2011 07:36:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66707#M921</guid>
      <dc:creator>hjwang</dc:creator>
      <dc:date>2011-08-30T07:36:01Z</dc:date>
    </item>
    <item>
      <title>Re: Script Alert Argument?</title>
      <link>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66708#M922</link>
      <description>&lt;P&gt;I am also looking for the same .. Any idea ?&lt;/P&gt;</description>
      <pubDate>Mon, 30 Apr 2012 21:41:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66708#M922</guid>
      <dc:creator>deepus2000</dc:creator>
      <dc:date>2012-04-30T21:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: Script Alert Argument?</title>
      <link>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66709#M923</link>
      <description>&lt;P&gt;It looks like there may be a way to do it but you'll have to make some modifications to config files and scripts.  I would recommend backing up any files first of course so you can roll back.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/32385/alert-script-and-severity"&gt;http://splunk-base.splunk.com/answers/32385/alert-script-and-severity&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Apr 2012 21:54:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66709#M923</guid>
      <dc:creator>sdaniels</dc:creator>
      <dc:date>2012-04-30T21:54:31Z</dc:date>
    </item>
    <item>
      <title>Re: Script Alert Argument?</title>
      <link>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66710#M924</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I was looking for the answer to the same question as yours, but I ended up with the use of $8, which is the path to the compressed search result as results.csv.gz in splunk's var/run/splunk/dispatch directory.&lt;/P&gt;

&lt;P&gt;Modifying the JS would also work, but I am afraid the modification you make probably will be overwritten when you upgrade the splunk software. &lt;/P&gt;

&lt;P&gt;Better check with Splunk support. &lt;/P&gt;</description>
      <pubDate>Tue, 21 Aug 2012 08:55:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66710#M924</guid>
      <dc:creator>melonman</dc:creator>
      <dc:date>2012-08-21T08:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: Script Alert Argument?</title>
      <link>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66711#M925</link>
      <description>&lt;P&gt;I hit upon the same issue and ended up using the powershell app to orchestrate the searches. This way I can pass unlimited arguments in via the REST API and handle the results in the PS script&lt;/P&gt;</description>
      <pubDate>Tue, 21 Aug 2012 10:41:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Script-Alert-Argument/m-p/66711#M925</guid>
      <dc:creator>Bulluk</dc:creator>
      <dc:date>2012-08-21T10:41:06Z</dc:date>
    </item>
  </channel>
</rss>

