...

Reports are created from predefined Report Templates. The templates individually implement which data will be processed when creating a report. Report Templates can be parameterized with the number of hits and the sorting (highest/lowest). At this stage It is not possible for users to create their own implementations for reports.

Find below the list of Report Templates that ship with JS7.

Prerequisites

Reports are created from a Java class that can be configured to use Java options. It is recommended to use the -Xmx<number><unit> option to limit Java heap space consumption. The default value is -Xmx64M., see JS7 - Settings.

Memory consumption depends on

• the Report Template,
• the frequency:  short frequencies such as a weekly interval will consume less memory than long frequencies such as a yearly interval,
• the value for the number of "Hits",
• the value for "Step Overlap": small values will consume more memory. The Step Overlap is configured for the "Top n periods with highest/lowest number of workflow/job executions" Report Templates.
• the duration of job/workflow runs for the "Top n periods with highest/lowest number of workflow/job executions" Report Templates.
• the number of distinct workflows/jobs, that are considered for counting, for example for the number of failed workflows.
• the number of distinct Agents in reports based on the "Top n Agents with highest/lowest number of parallel job executions" Report Templates.

Example: A report based on the "Top n periods with highest/lowest number of workflow/job executions" Report Template will consume more memory when using the frequency "Yearly" instead of "Monthly" or with a Step Overlap of 1m instead of 60m.

Report Templates

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

...