Did you know that log message filter settings are stored at the workspace level, not as part of the engine configuration?
Here's what the relevant section of an FMW file looks like:
Without debug:
LOG_FILENAME "$(FME_MF_DIR)none2none.log"
LOG_APPEND NO
LOG_FILTER_MASK -1
With debug enabled:
LOG_FILENAME "$(FME_MF_DIR)none2none2.log"
LOG_APPEND NO
FME_DEBUG MAPPING_FILE BADNEWS UNGROUPED UNCORRELATED DUMP_SCHEMA XSD_VERBOSE HTTP_DEBUG FTP_DEBUG FME_DEBUG STASH
LOG_FILTER_MASK -1
This setup makes sense, especially when publishing workspaces to FME Flow and needing consistent logging behavior.
However, in FME Workbench, this configuration is set under FME Options, which seems a bit out of place. It's not an engine or Workbench setting; it's specific to the workspace you're editing.
In FME 2024.1, there was a review of this area. Could we take it a step further and move this setting to Workspace Parameters? That way, it's clear and directly tied to the workspace itself.