Thanks Jon I finally understood how to apply 'report' once I understood how to use 'create' as a timer.
I apologize to everyone if it seems that I beat this one to death. I am now looking for strategies of handling events of unknown size and duration. So with the simple example below, how would I need to modify if I wanted to have different actions depending upon the cache depth? Lets say I want to examine the cache is of depth 10 or greater handle as 1 master event through the report. And if the cache depth is less than work through them one at a time. # # for a pattern foo\S+ create a context known as 'cache' if one doesn't exist # The cache lifetime is 30 seconds, so the create action 'report' dumps what # is in the cache after its lifetime expires. # type=Single ptype=Regexp pattern=foo(\S+) desc=report context=!cache action=create cache 30 (report cache /bin/cat ) # # for the same pattern foo\S+ if a context exists, add to it. # type=single ptype=Regexp continue=TakeNext pattern=foo(\S+) context=cache desc=pattern from $1 action=add cache $0 Tim Peiffer Network Support Engineer Office of Information Technology University of Minnesota/NorthernLights GigaPOP ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Simple-evcorr-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
