Question:
How can we setup our log files to be written to a database ?
Answer:
This is automatically done by JobScheduler: if you configure a database connection in ./config/factory.ini JobScheduler will create protocols for tasks and orders, have a look at the detailed log file documentation.
To name a few settings in ./config/factory.ini:
; 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 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 the job history to be searched and 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