Page History

...

• A setting for the applicable size of a task log (name: log_applicable_size, default: 500 MB). A task log that exceeds this size will be handled like this:
  • The first 100 KB and the last 100 KB of log output will be used as the task log.
    • A banner information is added to the begin of log output:
      • LOG OUTPUT EXCEEDS APPLICABLE SIZE OF <log_applicable_size> MB AND IS TRUNCATED TO THE FIRST AND LAST 100 KB.
    • The truncated task log will be compressed and added to the database.
  • The original log file will be removed.
  • Occurrence of log output exceeding this threshold raises a warning, however, the task execution history and truncated log output are available from the JOC Cockpit API and GUI.
• A setting for the maximum size of a task log (name: log_maximum_size, default: 1000 MB). A task log exceeding this size will be handled like this:
  • The History Service will stop to write larger log files. Log output exceeding the threshold value is ignored.
  • The first 100 KB of the log file will be used as the task log.
    • A banner information is added to the begin of log output:
      • LOG OUTPUT EXCEEDS MAXIMUM SIZE OF <log_maximum_size> MB AND IS TRUNCATED TO 100 KB.
    • The truncated task log will be compressed and added to the database.
  • The original log file will be removed.

The History Service similarly considers the above settings when performing switch-over and fail-over operations between JOC Cockpit instances (compressing and storing current logs to the database).

The JOC Cockpit GUI makes use of the following threshold setting, see JS7 - Settings:

• A setting for the maximum display size of a task log (name: log_maximum_display_size, default: 10 MB). An uncompressed task log exceeding this size is not offered for display with the Log View window but is offered for download only.

The threshold settings can be modified from the JOC Cockpit Settings page.

...