+4Is it possible to turn off log entries like these?
These just add clutter to the job reviewing process.
+5Hi
Thanks for the question!
Those log entries are helpful for the debugging process if you have any issues running jobs. That information may seem “too detailed”, but it’s very important to know the workspace version and potential memory issues. You are not able to remove them from the FME Flow job log files directly.
You could filter the job log using “warning”, “information” tags from the Flow UI, and it will only show the category you chose.
I hope it helps!
Cheers,
Skyler
+4I think your suggestion is reasonable in theory, but in practice it isn’t workable.
Based on the attached screenshot, it’s very difficult to quickly identify actual issues when the log is continually filled with these warnings.
The memory-related messages are particularly problematic, as I can’t add more physical memory to my instance without moving to a higher-cost tier.
I would recommend allowing users to disable logging for these types of messages. If that isn’t possible, they should at least be downgraded from warnings to informational messages. The details are interesting, but they aren’t actionable in a cloud environment.
| 3 | Workspace was last saved in FME version: FME 2025.1.3.1 (20251021 - Build 25645 - WIN64) |
| 23 | Failed to free sufficient memory to reach the process usage limit. To improve stability and performance please increase the memory available to FME. Available memory can be increased by adding physical RAM, increasing swap space, or closing other applications |
| 40 | FME Configuration: Extremely low initial memory conditions detected. To improve stability and performance please increase the memory available to FME. Available memory can be increased by adding physical RAM, increasing swap space, or closing other applications |
+5Hi
Thanks for the response. We understand that the repeated memory related warning messages in the log files could be distracting when you couldn't further upgrade more RAM.
Currently FME has an option to include additional information with log debug on. However, we don't have an option to "delete' certain warning messages. Those memory related warning messages could be helpful for debugging in other cases.
I recommend submitting an idea here if this is a helpful enhancement for you. https://community.safe.com/topic/new?type=idea I could also file an improvement ticket internally. However, the ideas submitted by the customer usually get more attention from the product managers.
I hope that helps.
Skyler
+48I’d certainly vote for an idea to be able to downgrade certain types of warnings, and then these not to show under Logs on the job overview screen in FME flow .
The aim for me is always to see no exclamation marks here, but superfluous warnings mean you get to the stage where you have to remember, Job A always returns 2 warnings so if it starts returning 3 that’s something to look at. Whereas Job B should return no warnings so if it returns 1 you need to look at it, and Job C returns 1 warning so if it returns 2 that’s something to look at etc. It becomes almost impossible to easily manage.
+24I’d certainly vote for an idea to be able to downgrade certain types of warnings, and then these not to show under Logs on the job overview screen in FME flow .
Agreed! Warnings from SQLCreators/SQLExecutors for example: “Table does not include a spatial column. Geometry will not be read” would be one of my favorites to be able to disable.
The aim for me is always to see no exclamation marks here, but superfluous warnings mean you get to the stage where you have to remember, Job A always returns 2 warnings so if it starts returning 3 that’s something to look at. Whereas Job B should return no warnings so if it returns 1 you need to look at it, and Job C returns 1 warning so if it returns 2 that’s something to look at etc. It becomes almost impossible to easily manage.
+1 This. I have dashboards and reports on scheduled workspaces, and it’s always a nightmare to determine whether I need to check the logs on one run or not.
