Using 2018.0 I placed a logger in-line with a translation. Max messages to log is set to 999999, but it stops logging after 115 features.
Why is that - and how do I get it to log all the translation info (looking for info on the 428'th item in this case)?
Best answer by davideagle
The Workbench parameter 'max features to log' takes precedence over the Logger's parameter. It's in the Navigator under 'Workspace Parameters', and appears to be default set to 200, so not sure why yours is different. Anyway, you appear to be able to ramp it up as high as 999999999 if you want to open the taps and then use the loggers to reign that limit in.
I've no idea why it stops logging at that particular point, but in my experience it's a bad idea to log that many features to the FME log, it's not meant for that purpose.
If you need to look at the 428th item in a workflow I'd rather recommend the following pattern:
You may also want to look into the breakpoint functionality in FME, it's extremely handy in cases like these: https://desktopmanualbasic.safe.com/DesktopBasic3BestPractice/3.17.FeatureDebugging.html
+22The Workbench parameter 'max features to log' takes precedence over the Logger's parameter. It's in the Navigator under 'Workspace Parameters', and appears to be default set to 200, so not sure why yours is different. Anyway, you appear to be able to ramp it up as high as 999999999 if you want to open the taps and then use the loggers to reign that limit in.
The Workbench parameter 'max features to log' takes precedence over the Logger's parameter. It's in the Navigator under 'Workspace Parameters', and appears to be default set to 200, so not sure why yours is different. Anyway, you appear to be able to ramp it up as high as 999999999 if you want to open the taps and then use the loggers to reign that limit in.
