https://community.splunk.com/t5/Getting-Data-In/scripted-input-execute-condition/m-p/81048#M16717 <P>I don't have an answer, per se, but I have some input:</P> <P>There's a magic value to interval in an inputs.conf script: specifier (I think it's zero) that means "run once on startup". But then you'd have to restart the forwarder a lot.</P> <P>If I were asked to implement this, I would put the logic in my script. I'd use a persistent state file (maybe in $SPLUNK_HOME/var/lib/splunk/persistentstorage) to keep track of the last stamp we'd seen, then use this script to inspect the file on each run. Most executions of the script are going to be no-ops "data hasn't changed!", but when it does execute the decoding loop, you'll want to make sure that the interval of the script is longer than the amount of time a single run would take. Splunk <EM>shouldn't</EM> start a second instance until the first is done, but I would schedule my runs so that I didn't have to rely upon that.</P> Thu, 16 Jan 2014 17:15:39 GMT sowings 2014-01-16T17:15:39Z https://community.splunk.com/t5/Getting-Data-In/scripted-input-execute-condition/m-p/81047#M16716 <P>Hello,</P> <P>We are working towards a scripted input of AIX errpt messages and would like to kick the script off whenever it notices the timestamp changes, ie. when a new event is added. The file is binary so we need to have a custom script to run first to decode the data then dump it to a file. Any idea on how to do a conditional script interval in inputs.conf? Also, if you have seen a better way to aggregate errpt messages please feel free to share. Thanks!</P> Thu, 03 Oct 2013 12:32:16 GMT https://community.splunk.com/t5/Getting-Data-In/scripted-input-execute-condition/m-p/81047#M16716 aaronkorn 2013-10-03T12:32:16Z https://community.splunk.com/t5/Getting-Data-In/scripted-input-execute-condition/m-p/81048#M16717 <P>I don't have an answer, per se, but I have some input:</P> <P>There's a magic value to interval in an inputs.conf script: specifier (I think it's zero) that means "run once on startup". But then you'd have to restart the forwarder a lot.</P> <P>If I were asked to implement this, I would put the logic in my script. I'd use a persistent state file (maybe in $SPLUNK_HOME/var/lib/splunk/persistentstorage) to keep track of the last stamp we'd seen, then use this script to inspect the file on each run. Most executions of the script are going to be no-ops "data hasn't changed!", but when it does execute the decoding loop, you'll want to make sure that the interval of the script is longer than the amount of time a single run would take. Splunk <EM>shouldn't</EM> start a second instance until the first is done, but I would schedule my runs so that I didn't have to rely upon that.</P> Thu, 16 Jan 2014 17:15:39 GMT https://community.splunk.com/t5/Getting-Data-In/scripted-input-execute-condition/m-p/81048#M16717 sowings 2014-01-16T17:15:39Z