Maybe I'm completely confused, but what I had understood that you wanted was something like the following:
- loadrunner is writing to an output file as it runs (say output.log)
- your program reads from output.log looking for interesting results.
Normally the difficult part of this is getting the second program to continue reading when new data is written to the file. That is what File::Tail helps with.
Now it sounds like you have a few other issues to consider.
- some form of logging requirement
- notify you on interesting events
- requirement to check if requests take too long
I can't tell if you need the logging in its own right, or if you just need it for the notification. If you just need the notifications, there are many methods that can be used (email, Log::Log4perl, flashing lights, etc.). If you need the log itself, then either writing to a file directly or one of the logging modules on CPAN would work.
Checking to see if a process is taking too long is could be handled with a timeout on the read. File::Tail can handle this using the maxinterval parameter. If File::Tail doesn't suit your needs, you could wrap the read in an eval and use the alarm function to make certain you don't wait too long. (If you time out, you can notify and loop back to wait some more.)
At this point, it would probably be worthwhile to try to write down (possibly just for yourself) the process you are trying to implement. From this end, it looks a bit fuzzy. Possibly writing out the events you are looking for and how you want to handle them would help. Then, some of the techniques I've mentioned may make more sense.
| 