JS7 does not make use of files for log output of order logs and task logs, see JS7 - Order Logs and Task Logs. JS7 instead streams log output from Agents to the Controller and to JOC Cockpit without use of 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.
To support a situation when log output should be consolidated to files 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 is used for the below examples with Linux and Windows. Users are free to use the JS7 REST Web Service from their preferred scripting language to provide similar functionality.
For similar handling of order logs see JS7 - How to make order logs available from files.
The following cmdlets are provided:
Access Log Object
Get-JS7TaskHistorycmdlet returns history results that can be filtered by folders, workflows, date range, jobs, see cmdlet description. By default today's task executions are returned.
Get-JS7TaskLogcmdlet is used in a pipeline and returns the task log object for each history entry.
- As a result the
$logsarray holds the list of task log objects.
A task log object carries a number of attributes as visible from the following console example:
Write Log to File
Reads the logs of today's tasks and writes the logs to a common file.
Reads the logs of tasks that completed within the last 8 hours and writes the log output to individual files in the
The log file names are created from the start time and from the job name of each task.
Provides a mechanism to subsequently retrieve previous logs. Starting from initial execution of the
Get-JS7TaskHistorycmdlet the resulting
$lastHistoryobject is used for any subsequent calls.
Consider use of the
Tee-Objectcmdlet in the pipeline that updates the
$lastHistoryobject that can be used for later executions of the same pipeline.
This pipeline can e.g. be executed in a cyclic job.
Automate Log File Creation
A workflow is created that runs the above commands in a cycle. The workflow operates 24/7 and writes task logs to files.
- The first job
get-history-task-logsis executed at the point in time when the order arrives that starts the workflow.
- This job determines the last history entry from which to start.
- The second job
write-task-logs-to-filesis executed within a JS7 - Cycle Instruction:
- The above example implements a ticking cycle every 30 minutes. For a 24h period the job will repeat every 30 minutes.
- Users can adjust the cycle at their will.
The first job
get-history-task-logs looks like this:
- Line 1: The shebang is required to identify PowerShell being the interpreter of the script. The above example is for Unix, for Windows the first line of the job script should be replaced as follows:
- Line 4: The are a number of ways how to specify details for a JS7 connection, see JS7 - How to connect to JOC Cockpit using the PowerShell Module.
- The host and port are specific for a user's environment.
- The Controller ID is specified during installation of the Controller and defaults to
- Line 9:
- A workflow variable is created that carries the list of task log objects returned by
the Get-JS7TaskHistorycmdlet for which task logs should be created. This variable is in fact a PowerShell object that is serialized to JSON and prefixed with the string
json:for later use with the second job in the workflow.
The second job
write-task-logs-to-files looks like this:
- Lines 1, 4: Same explanations as for the previous job.
- Lines 7: The variable holding the list of task log objects of the last processing of this job is restored from a temporary file that holds the JSON representation of the objects. The temporary files is provided by the JS7 Agent and is referenced from an environment variable that is assigned the workflow variable like this.
Line 10: When reading the task history then the variable carrying the list of task log objects is updated and is forwarded to the workflow for next execution of the cycle.