Server Logs - how to follow a trace?

OL Connect 2024

I’m trying to understand how to follow a chain of events in the server logs. From file upload, to PDF output. I hope someone from the staff could explain it to me.
I’m referrint to the logs generally located at C:\Users\<user>\Connect\logs\

For the purpose of this analysis the input is a data file and the output is a PDF, we feed the data file through a Datamapper chained to a Template, Job and Output presets.

Current settings are default, so logging level is set to INFO.

All log files are names as <ENGINE>-TIMESTAMP-(<TEMPORARY REPOSITORY ID>).log like
Datamapperengine-2024-09-21-(4576).log

Datamining

The datamining logs at some point mention the configuration name and the filestore datafile infos. As long as the file ID being processed is saved I can pinpoint in the logs when and what happened during a datamining operation.

Also at the end of the operation the data set id produced is written to the log.

So Datamining is covered.

Mergeengine

Merge engine logs mention the template file being used, but there is no mention of which data set is being processed.

Also there is no mention of the content set id produced.

Weaver

Here only the output file and path is mentioned, there is no mention of content set being processed nor job set ids being produced.
It is my understanding that the weaver engine represent both the Job and Output steps so I would at least expect see mentioned the content set being processed.

The upcoming 2024.2 release will contain logging improvements which should greatly improve the situation in this area.

1 Like

Love it! Will wait for the update then since I am in no hurry.

Once you get your hands on it, we’d be happy to have your feedback on it.

OT: is there a newsletter to be promptly notified of the new release? Couldn’t find anything on the hompage.

The news appears in the OL Connect Designer’s welcome screen. You can also subscribe to the technical blog to be notified without having to open up the application.