Hi Paul,
Ah, the ever repeating requirement to parse log files. In general, its too bad when it comes to that, but I realize that sometimes that is what people wanted. Long ago Peter Laulund suggested the idea of being able to run some Tcl after a translation ends, and that that Tcl could have access to a number of things that might either alleviate or at least lessen the problem of parsing log files. The examples here: http://www.fmepedia.com/index.php/Category:TCL_Sample Contain some relevant ideas, particularly example 5, which shows how to sweep through the logfile in the end Tcl, keying on the message numbers: http://www.fmepedia.com/index.php/Pre_and_Post_Processing_Scripts:_Examp le_5 Anyway, I'd recommend that, but I'd first want to ensure that the predefined variables we provide don't give enough information. More pointers to the whole FME_END_TCL can be found here: http://www.fmepedia.com/index.php/Category:TCL_Pre_Post_Processing_FAQ And the complete doc is here: http://www.safe.com/support/online-documentation/Fundamentals/fme_config uration%20-%20FME_BEGIN_TCL%20and%20FME_END_TCL.htm Dale > We're working on a project which needs to do good event reporting based > on happenings inside an FME process. > > - Does anyone have any tools for FME log parsing they like? Best practices? > - Is Safe Software going to make the lots a little more structured some > day? Factories in particular could use some more standardized reporting. >
