Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Minor corrections to text

...

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

Answer:

Starting with Version 1.7 you can only use JobScheduler with a database. This was an option with older versions.

Both the older and newer versions of JobScheduler automatically write their log files to the database - specification of the database connection in the This is automatically done by JobScheduler: if you configure a database connection in ./config/factory.ini JobScheduler will file was sufficient for older JobScheduler versions (i.e. 1.6.x and older) to create protocols for tasks and orders , have a look at in the database. See also the detailed log file documentation.

To name a few The most important settings in the ./config/factory.ini file are:

Code Block
  ;                         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

...