https://community.splunk.com/t5/Getting-Data-In/syntax-for-scripted-input-in-inputs-conf/m-p/92257#M19172 <P>You can parameterize the scripted inputs. I've used this several times. So if you configure the scripted input this way</P> <PRE><CODE>[script://./bin/runmycmd.sh cmd] </CODE></PRE> <P>the value "cmd" will be avaiable to the script in the variable <CODE>$1</CODE>.</P> Fri, 19 Nov 2010 20:40:32 GMT ziegfried 2010-11-19T20:40:32Z https://community.splunk.com/t5/Getting-Data-In/syntax-for-scripted-input-in-inputs-conf/m-p/92256#M19171 <P>Am I correct in thinking that</P> <PRE><CODE>[script://./bin/runmycmd.sh cmd] </CODE></PRE> <P>will not work?</P> <P>I'd like to be able to hand the variable cmd to runmycmd...</P> Fri, 19 Nov 2010 09:34:36 GMT https://community.splunk.com/t5/Getting-Data-In/syntax-for-scripted-input-in-inputs-conf/m-p/92256#M19171 bfaber 2010-11-19T09:34:36Z https://community.splunk.com/t5/Getting-Data-In/syntax-for-scripted-input-in-inputs-conf/m-p/92257#M19172 <P>You can parameterize the scripted inputs. I've used this several times. So if you configure the scripted input this way</P> <PRE><CODE>[script://./bin/runmycmd.sh cmd] </CODE></PRE> <P>the value "cmd" will be avaiable to the script in the variable <CODE>$1</CODE>.</P> Fri, 19 Nov 2010 20:40:32 GMT https://community.splunk.com/t5/Getting-Data-In/syntax-for-scripted-input-in-inputs-conf/m-p/92257#M19172 ziegfried 2010-11-19T20:40:32Z https://community.splunk.com/t5/Getting-Data-In/syntax-for-scripted-input-in-inputs-conf/m-p/92258#M19173 <P>This worked. A warning for all, 'cmd' had to be the full path to the cmd file. For instance $SPLUNK_HOME/etc/apps/appname/bin/cmd</P> <P>Thanks!</P> Thu, 25 Nov 2010 11:14:46 GMT https://community.splunk.com/t5/Getting-Data-In/syntax-for-scripted-input-in-inputs-conf/m-p/92258#M19173 bfaber 2010-11-25T11:14:46Z