Introduction

There are predefined Report Templates. The template determines which data will be analyzed for the report. All Report Templates can be parameterised with the number of hits and the sorting (highest/lowest). 

Report Templates

Report Template: Top n workflows with highest/lowest number of failed executions

The Report Template counts failed workflow executions:

• A workflow execution is considered being failed if the order leaves the workflow with an unsuccessful outcome, for example if an order is cancelled or if a JS7 - Finish Instruction is used indicating unsuccessful outcome.
• A workflow is not considered being failed just because some jobs failed, for example if a JS7 - Retry Instruction is used a later retry of a job can be successful. Instead, the resulting history status of an order is considered.

Report Template: Top n jobs with highest/lowest number of failed executions

The Report Template counts failed job executions.

• Shell job execution is considered being failed based on a job's exit code and optionally output to the stderr channel.
• JVM job execution is considered being failed based on the job's outcome that can hold exceptions.

Report Template: Top n Agents with highest/lowest number of parallel job execution

The Report Template counts parallel job executions with Agents. A Job A is considered in parallel to Job B if

• Job A starts after Job B has started and before Job B will end or
• Job A ends after Job B is started and before Job B will end.

Report Template: Top n high criticality jobs with highest/lowest number of failed executions

The Report Template counts failed executions of jobs with criticality critical. The criticality is a job attribute, see JS7 - Job Instruction.

Counting is performed similar to Report Template: Top n jobs with highest/lowest number of failed executions.

Report Template: top n workflows with highest/lowest number of failed executions for cancelled orders

The Report Template counts failed workflow executions due to orders that have been cancelled.

The cancel operation is applied to an order by user intervention .

Report Template: Top n workflows with highest/lowest need for execution time

The Report Template considers the duration of successful workflow execution. Failed workflow executions will not be considered.

Report Template: Top n jobs with highest/lowest need for execution time

The Report Template considers the duration of successful job execution. Failed job execution will not be considered.

Report Template: Top n periods with highest/lowest number of workflows executions

The Report Template divides the Reporting Period into sub-periods. The length of sub-periods is determined by the "Period Length" setting in the JS7 - Reports - Configuration. The start of the next sub-period is determined by the "Period Step" setting in the Report Configuration.

Example: 

• Period Length: 5m
• Period Step: 2m
  • 00:00:00-00:05:00
  • 00:07:00-00:12:00
  • 00:14:00-00:19:00 

The number of jobs started is counted per period.

Report Template: Top n periods with highest/lowest number of workflows executions

The Report Template divides the Report Period into sub-periods. The length of sub-periods is determined by the "Period Length" setting in the Report Configuration. The start of the next period is determined by the "Period Step" setting in the Report Configuration.

The number of orders being processed by a workflow is counted per period.

Report Template: Top n jobs with highest/lowest number of successful executions

The Report Template counts jobs that completed successfully. Failed jobs are not considered.

For possible reasons of failure see Report Template: Top n jobs with highest/lowest number of failed executions.

Report Template: Top n workflows with highest/lowest number of successful executions

The Report Template counts workflows that completed successfully. Failed workflow executions are not considered.

For reasons of failure see Report Template: Top n workflows with highest/lowest number of failed executions.