Having a second log is pretty non-standard, and obscures the ordering of events that may be pertinent. So I am not thrilled with that idea. However, the current logging system does not make it easy to determine where a log message is coming from, nor can you filter log messages with grep easily.
It would be better to include enough information in the ONE manifoldcf.log file so that you know what connector the log message is coming from. We already have individual loggers set up that are "catch all" buckets for events of various kinds, but the logger itself might want to have more information, e.g. the class that did the logging, as an optional argument. Or - we could use log4j's native capabilities. All that is needed to do that is to simply create a static logger in every connector class from which you wish to log, and write directly to that one. Karl On Tue, Jan 18, 2022 at 10:29 AM Julien Massiera < julien.massi...@francelabs.com> wrote: > Hi all, > > > > In order to improve the tracking of documents processing status, and in > particular when something goes wrong with MCF (like hanging processes > without obvious causes), I would like to propose to add specific logs into > each repository connector. One log at the beginning of each > documentIdentifier processing in the processDocuments method, and one at > the > end, so that, at any time, we can easily tell which documents are being > processed. > > To implement that, I was thinking of a common class that would write the > logs, with a custom log level (between INFO and DEBUG), so that the logs > could be easily isolated into a specific file through log4j conf. The class > would be stored in the org.apache.manifoldcf.crawler.system package like > the > Logging class. > > > > What do you think about that ? > > > > Regards, > > Julien > >
