Skip to main content

In FME Server 2019, when you added a Log action, it ran a workspace that was installed with FME Server. You had to specify the location and also whether to overwrite or append.

In FME Server 2020.0.1, there have been some changes. You no longer specify a location and you don't have the option to append. Since I imported a backup into the new instance, I also have the previous log and filter workspaces so I cannot check now whether these were also available with the install of FME Server 2020. Is the Log action now native to Automations and does not run a workspace, and thus does not consume an engine? I don't see a Log workspace listed in the completed jobs so I assume that is the case.

Which brings me to my main question: Where do these logs actually go? I know they can be downloaded, but I would like to know where I can get to them outside of having to view them and then download. I looked in Resources\\Logs, but cannot find anything. Also is there a way to append vs. overwrite each time an automation is restarted? Thanks.

As far as I can tell, the automation logs are not stored in text files like the FME Server logs.

You will find the automation logs in the FME Server system database, in the table "fme_automation_log" with associated tables. If you are using the default system database, you can access it with a PostgreSQL reader.


As far as I can tell, the automation logs are not stored in text files like the FME Server logs.

You will find the automation logs in the FME Server system database, in the table "fme_automation_log" with associated tables. If you are using the default system database, you can access it with a PostgreSQL reader.

Thanks a lot @david_r, that explains why I couldn't find anything in the Log folders 🙂 Honestly it has made getting to the data within the logs much more efficient now, although you have to understand that you'll lose the data each time the automation is re-enabled.


Reply