...

For the given workflow the order log Order Log can look like this:

Explanation:

• The top of the screen offers a number of options:
  • and will expand and collapse log output of any jobs executed for the workflow.
  • and will expand and collapse output of the selected job.
  • Main: displays/hides lines holding information start times, job names etc. that are using the [MAIN] qualifier.
  • Success: displays/hides lines holding success messages using the [SUCCESS] qualifier. Such lines use the green color.
  • stdout: displays/hides log output from jobs written to the stdout channel.
  • Debug: displays/hides log output from JVM jobs writing debug messages, see JS7 - Job Classes.
  • Detail: displays/hides details about events, for example the timestamp when an order is forking and when child orders are joining. Such lines use the blue color.
• On the right side of the screen users find the icon that opens the navigation panel:
  • The panel displays jobs and other JS7 - Workflow Instructions in historical sequence.
    • If a job fails and is repeated then it will occur a number of times.
    • The navigation panel displays the hierarchy of workflow instructions.
  • and will expand and collapse the navigation panel for nested workflow instructions.
  • Clicking a specific job or instruction in the navigation panel will highlight the log output related to the instruction.
• If jobs are running on Agents that make use of different time zones, then users can specify timestamps in log output to be converted to their time zone, see JS7 - Profiles - Preferences. Otherwise the original timestamps of the Agent processing the job or Agent/Controller processing the instruction will be displayed.

Task Log

For a given job the task log Task Log can look like this:

Explanation:

• Use of checkboxes is similar to display of the Order Log.
• Outo

Running Log

A Running Log represents the fact that an Order Log or Task Log is displayed for a running order or task. Any output created by the order / task is immediately made available.

...

• Log output is created
  • from jobs that write to the stdout or stderr channels,
  • from events that signal processing of instructions such as a job start, forking / joining of an order etc.
• Log output is displayed in historic sequence.
• If jobs are running on Agents that make use of different time zones, then users can specify timestamps in log output to be converted to their time zone, see JS7 - Profiles - Preferences. Otherwise the original timestamps of the Agent processing the job or instruction will be displayed.

Availability of Logs

Streaming of Logs

...

Task Logs are completed when tasks are terminated. At that point in time the task log Task Log is persisted to the database by the History Service running in JOC Cockpit. 

Order Logs are completed when all tasks and other workflow instructions have been processed and when the order is completed. At that point in time the Order Log is persisted to the database.

Before completion log output of tasks is Task Logs and Order Logs are stored to temporary files in the JOC Cockpit's <JETTY_BASE>/logs/history directory. This translates to the fact that only the active JOC Cockpit instance can serve to users the logs for which processes are still running. A standby JOC Cockpit instance has no access to temporary files.

Cluster Operation

The History Service of the active JOC Cockpit instance persists Task Logs and Order Logs.

This includes that the active JOC Cockpit instance in a cluster will receive log output onlyfrom the Controller. When using a standby JOC Cockpit instance in a cluster then no Running Log is available ., Instead, logs become available after completion of orders and tasksand logs are not available before completion.

In a situation when we find a switch-over between an active and a standby JOC Cockpit instance, the order logs and task logs are zipped Order Logs and Task Logs will be stored to the database and are in a compressed format and will be removed from disk the file system by the previously active JOC Cockpit instance. The newly active JOC Cockpit instance will unzip extract related logs from the database and will store them with JOC Cockpit's file system.

In case of fail-over, for example in case of a crash of JOC Cockpit, the standby JOC Cockpit instance will become active and will ask the Controler to repeat delivery of log output for any Task Logs and Order Logs that have not been persisted in the database.