Skip to main content
Question

How to set the maximum file size for logs from FME Desktop?


2020-08-20_11-56-27I have some FME Workbenches that run frequently (i.e. every minute) and the logs are always working great if I find an error or need to check up on a specific run. I run the workbenches through task scheduler. The log file just keeps growing, and will only refresh if I delete the log file. This is taking up literally gigabytes of space.

 

I'd like to set the maximum file size for the log file - for example, one MB. That way I can see all recent log files (i.e. logs from the last few days) but I don't have to keep any of the really old logs, and they can get removed automatically as new logs come through.

 

I know you can set the "max features to record" for a log, but I don't see anything about limiting the actual log file. From what I've seen so far, changing the max features to record doesn't limit how big the log file can be.

 

Anyone have suggestions for this?

 

3 replies

davtorgh
Contributor
Forum|alt.badge.img+10
  • Contributor
  • August 20, 2020

Hi @karenfirstname​ ,

 

I suggest to check inside FME Options (Tools menu) if "Append to Log File" is checked. Maybe you want to check "Save Log to File".

 

screenshot

 

Hope that helps!


mark2atsafe
Safer
Forum|alt.badge.img+43
  • Safer
  • August 21, 2020

I don't believe there is a parameter, setting, or option for this. I think you should probably file this as an Idea (click the Ideas button at the top of this page) and encourage other users to vote for it. That way it will get more recognition the next time we review Ideas for adding to the product.


mark2atsafe
Safer
Forum|alt.badge.img+43
  • Safer
  • August 21, 2020
davtorgh wrote:

Hi @karenfirstname​ ,

 

I suggest to check inside FME Options (Tools menu) if "Append to Log File" is checked. Maybe you want to check "Save Log to File".

 

screenshot

 

Hope that helps!

This might help, but if the user is running workspaces from Task Scheduler, they might need to append to the log file to keep all of the task logs.

 

The solution would be to set the log file name in Workbench. If that workspace parameter was set with (for example) a Python Scripted Parameter, then it could set the log name to [datetime].log - that way each run would write a separate log and append wouldn't be needed.


Reply


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