Introduction

Order logs and task logs are stored in the JS7 - Database in a compressed format and are available from the JS7 - Order History and JS7 - Task History views respectively. Both views allow display of the log output in a log view window.

JS7 does not make use of files for log output of order logs and task logs.

• Files are a frequent source of error as they may not be created due to disk space restrictions or lack of permissions.
• Job processing could be blocked if a log file cannot be created. Even worse, if log files are not available then users are unable to see job execution results.

JS7 therefore streams log output from Agents to the Controller and to JOC Cockpit without the use of files.

• Streaming makes job log output available to JOC Cockpit within 1s. 
• Streaming allows a running log which translates to the fact that users observe ongoing log output of orders and jobs in the log view window.
• In case of missing connections:
  • between Controller and Agent - the Agent stores log output in its journal and forwards logs when reconnected to a Controller later on. 
  • between JOC Cockpit and Controller - the Controller stores log output in its journal and forwards logs when reconnected to JOC Cockpit at a later point.

Log Files

A number of users prefer to have log files available for each order execution and job execution, for example to consolidate log files on a file server or to submit log files to specific tools for log analysis.

• Log analysis is useful but usually comes too late. It's more a reporting activity that is not intended to replace near-real time monitoring.
• Log analysis starts when the log is completed. In Unix environments parallel read and write operations on log files can occur. 
• Log analysis is useful when it comes to parsing logs for unexpected output or errors. However, it might prove tedious to teach a log analyzer recovery of errors from log output in case of a job being successfully restarted for a specific order.

The JS7 - REST Web Service API allows access to log output of orders and jobs and thereby supports a situation when log output should be consolidated or should be analyzed by external tools.

The JS7 - PowerShell Module is a lightweight wrapper for the REST Web Service API that can be used with Linux and Windows to provide order logs and task logs from files as described in the linked articles below. Users are free to use the JS7 REST Web Service from their preferred scripting language to provide similar functionality.

Links

How To ... Instructions

Frequently Asked Questions