https://community.splunk.com/t5/Getting-Data-In/Checkpointing-scripts-for-subsequent-invocations/m-p/76188#M15548 <P>I'm writing an Add-on script for the universal forwarder that will read several log files containing complex data and reformat the data so that Splunk can more easily parse it. </P> <P>Does my script need to implement it's own logic for "where it left off last time it was invoked" or does Splunk help with that somehow? </P> <P>In other words, is it possible to have 'monitor' functionality, but with my own custom script?</P> <P>Thanks.</P> Thu, 07 Apr 2011 05:28:37 GMT dveith 2011-04-07T05:28:37Z https://community.splunk.com/t5/Getting-Data-In/Checkpointing-scripts-for-subsequent-invocations/m-p/76188#M15548 <P>I'm writing an Add-on script for the universal forwarder that will read several log files containing complex data and reformat the data so that Splunk can more easily parse it. </P> <P>Does my script need to implement it's own logic for "where it left off last time it was invoked" or does Splunk help with that somehow? </P> <P>In other words, is it possible to have 'monitor' functionality, but with my own custom script?</P> <P>Thanks.</P> Thu, 07 Apr 2011 05:28:37 GMT https://community.splunk.com/t5/Getting-Data-In/Checkpointing-scripts-for-subsequent-invocations/m-p/76188#M15548 dveith 2011-04-07T05:28:37Z https://community.splunk.com/t5/Getting-Data-In/Checkpointing-scripts-for-subsequent-invocations/m-p/76189#M15549 <P>If you script is being run as a scripted input, then you will need to maintain last-run state for yourself. Some of Splunk's own scripted inputs (like in the *nix app) do this as well - by keeping a file with an epoch time stored in it.</P> Fri, 08 Apr 2011 04:14:52 GMT https://community.splunk.com/t5/Getting-Data-In/Checkpointing-scripts-for-subsequent-invocations/m-p/76189#M15549 dwaddle 2011-04-08T04:14:52Z