Skip to end of metadata
Go to start of metadata


How can we setup our log files to be written to a database ?


Starting with release 1.7 JobScheduler requires a database, see  JS-1143 - Getting issue details... STATUS

JobScheduler writes log files to the database for which a connection is configured with the ./config/factory.ini file. This includes logs for tasks and orders, see log file documentation.

Settings in the ./config/factory.ini file include:

  ;                         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 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 display log file content. You can remove the log files from disk and keep them in the database.