You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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 respectively. This includes to display 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 might not be created due to restrictions of disk space or permissions.
  • If a log file cannot be created then this could block processing of jobs. Even worse, if log files are not available then users are blind about job execution results.

JS7 therefore streams log output from Agents to the Controller and to JOC Cockpit without 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 then the Agent stores log output in its journal and forwards logs when reconnected to a Controller later on. 
    • between JOC Cockpit and Controller then the Controller stores log output in its journal and forwards logs when reconnected to JOC Cockpit later on.

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 that a job was successfully restarted for a specific order.

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

The JS7 - PowerShell Module is a lightweight wrapper for the REST Web Service API that can be used with Linux and Windows to provide orders logs and task logs from files, see Links. 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



  • No labels