How can we setup our log files to be written to a database ?
Starting with Version release 1.7 you can only use JobScheduler with a database. This was an option with older versions.requires a database, see
JobScheduler writes Both the older and newer versions of JobScheduler automatically write their log files to the database - specification of the database connection in the for which a connection is configured with the
./config/factory.ini file was sufficient for older JobScheduler versions (i.e. 1.6.x and older) to create protocols file. This includes logs for tasks and orders in the database. See also the detailed , see log file documentation.
The most important settings Settings in the
./config/factory.ini file areinclude:
; enable job history, if set to yes the ; scheduler keeps a job history in ; csv files or database tables history = yes ; store job protocol for task history ; (yes|no|gzip, default: no) history_with_log = gzip ; store job protocol for order history ; (yes|no|gzip, default: no) order_history_with_log = gzip ; store protocol for scheduler history ; (yes|no|gzip, default: no) history_archive = gzip
This examples specifies protocols logs to be stored in blob columns of the database in a gzip format, for a complete list of settings see the factory.ini reference documentation. Both the JobScheduler Operations Center (JOC) web interface and the JobScheduler Information Dashboard (JID) allow to retrieve the job history and to be searched and display log file content to be shown. You can remove the log files from disk and keep them in the database.
We provide a set of standard jobs concerned with logging and cleanup as part of our JITL jobs. These jobs rotate logs, remove debug entries from logs in the database and gzip log files on disk. ... read more