<?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: manually run a scripted input? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64213#M12907</link>
    <description>&lt;P&gt;If you write the output to a file in a sinkhole like, .../var/spool/splunk, then Splunk will consume it.&lt;BR /&gt;
If you need the sourcetype to be the same as when it runs as a script then create a different sinkhole and specify the sourcetype&lt;/P&gt;</description>
    <pubDate>Fri, 14 Dec 2012 14:59:07 GMT</pubDate>
    <dc:creator>itinney</dc:creator>
    <dc:date>2012-12-14T14:59:07Z</dc:date>
    <item>
      <title>manually run a scripted input?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64211#M12905</link>
      <description>&lt;P&gt;I have a scripted input in Splunk that sends it's data to Splunk via STDOUT. Is there any way to run the script on-demand and have the results sent to Splunk without restarting Splunk? Something like a "oneshot" cli method, but for scripted inputs, not for files.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Dec 2012 14:36:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64211#M12905</guid>
      <dc:creator>jeff</dc:creator>
      <dc:date>2012-12-14T14:36:25Z</dc:date>
    </item>
    <item>
      <title>Re: manually run a scripted input?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64212#M12906</link>
      <description>&lt;P&gt;What OS are you running?&lt;/P&gt;</description>
      <pubDate>Fri, 14 Dec 2012 14:52:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64212#M12906</guid>
      <dc:creator>alacercogitatus</dc:creator>
      <dc:date>2012-12-14T14:52:50Z</dc:date>
    </item>
    <item>
      <title>Re: manually run a scripted input?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64213#M12907</link>
      <description>&lt;P&gt;If you write the output to a file in a sinkhole like, .../var/spool/splunk, then Splunk will consume it.&lt;BR /&gt;
If you need the sourcetype to be the same as when it runs as a script then create a different sinkhole and specify the sourcetype&lt;/P&gt;</description>
      <pubDate>Fri, 14 Dec 2012 14:59:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64213#M12907</guid>
      <dc:creator>itinney</dc:creator>
      <dc:date>2012-12-14T14:59:07Z</dc:date>
    </item>
    <item>
      <title>Re: manually run a scripted input?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64214#M12908</link>
      <description>&lt;P&gt;or same idea with saving the result of the script to a file and monitor the file with the correct sourcetype.&lt;/P&gt;

&lt;P&gt;then you will have to clean the result file once a while.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Dec 2012 15:20:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64214#M12908</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2012-12-14T15:20:20Z</dc:date>
    </item>
    <item>
      <title>Re: manually run a scripted input?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64215#M12909</link>
      <description>&lt;P&gt;You can &lt;STRONG&gt;disable&lt;/STRONG&gt; and again &lt;STRONG&gt;enable&lt;/STRONG&gt; scripted input. This will make it run. It worked for me.&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2017 16:29:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64215#M12909</guid>
      <dc:creator>tomasmoser</dc:creator>
      <dc:date>2017-05-18T16:29:52Z</dc:date>
    </item>
    <item>
      <title>Re: manually run a scripted input?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64216#M12910</link>
      <description>&lt;P&gt;You can do this, but splunk wont index the data necessarily: &lt;CODE&gt;./splunk cmd /opt/splunk/etc/apps/yourapp/bin/script.sh&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;You will see STDOUT/ERR from your script though&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2019 12:47:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/manually-run-a-scripted-input/m-p/64216#M12910</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2019-07-17T12:47:57Z</dc:date>
    </item>
  </channel>
</rss>

