Skip to main content
Open

Move log message filter settings from FME options to Workspace parameters

Related products:FME Form
danilo_fme
mferwerda3
soeren
  • danilo_fme
    danilo_fme
  • mferwerda3
    mferwerda3
  • soeren
    soeren

alexbiz
Enthusiast

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.

2 replies

rylanatsafe
Safer
Forum|alt.badge.img+13

Hi @abizien , thank you for your feedback!

I wanted to note that, in FME Flow, we now support enabling the Log Debug setting in Run Workspace, Schedules, Streams, and Flow Apps. (We will be adding support within Automations in a later release.) 

We found that many customers unknowingly had published their FME workspaces to FME Flow with the debug enabled—which, in some cases, caused performance issues in production deployments. 

I believe that if you do not re-save the FME workspace in 2024.1 or newer (or if you e.g. upgrade FME Flow and import the backup), then the log setting “embedded” in the FME workspace should still be honoured.

 

While we think the new setting in Flow (per workspace, per feature) will offer more flexibility, I will take your feedback back to the team to see if we can improve it further or find a balance between the old behaviour and new behaviour (in both Form and Flow).


LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • August 15, 2024
NewOpen

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings