Workflow Insights Dashboard Options

All Workflow Insights dashboards enable you to address a business challenge. These challenges are described at the top of each dashboard topic:

Workflow Health Dashboard
Workflow Trends and Peak Volumes Dashboard
Workflow Distribution Dashboard
Workflow Alerts Dashboard
Workflow Definition Updates Dashboard
SLA Management Services Dashboard
Optimization Insights Dashboard
Job Execution Dashboard

Dashboard filters enable you to focus on the information you want to explore. All dashboards have the following filters:

Time Filter: Enables you to select a historical time period, such as the Last 24 hours, Last 7 days, Last 30 days, and Last year.
Filters: Enables you to set a wide range of filters by selecting parameters, such as Application is MyApp or by clicking on a specific data point in a dashboard panel.
Search: Enables queries that use logical operators, such as AND, OR, and NOT between fields, such as JobName:job* AND Application:App1 or Application:App2.

After you have achieved the desired view using filters, you can click Saved Queries and designate a name, allowing you to quickly return to the view later.

Workflow Health Dashboard

The Workflow Health dashboard enables you to ensure the robustness of the Control-M business processes.

The following table describes the panels in the Workflow Health dashboard:

Panel	Description
Executions success rate	Shows the percentage of executions Ended OK divided by Total Executions. The execution success rate rounds up to 100% when failures are less than 0.0001 of successes.
Total executions	Shows the volume of job executions.
Total executions Ended OK	Shows the volume of jobs that ended OK.
Daily executions Ended Not OK	Shows the total jobs failures per day, displayed over time. Each point on the graph is an aggregation of total daily executions that ended Not OK.
Top 10 Jobs that had the highest number of executions that Ended Not OK	Shows the top 10 jobs that failed the most times. The aggregation includes jobs with the same name in different servers, folders, Applications or Sub-Applications. For details of the server, folder, Application, and Sub-Application of each job, see the Jobs that had the highest number of executions that Ended Not OK table.
Jobs that had the highest number of executions that Ended Not OK	Shows the list of job with the highest number of failures. Table limits: Job Name: 1000 Control-M Server: 3 Folder: 4 Application: 1 Sub-Application: 1 Job Type: 1 Host: 1
Top 10 Applications that had the highest number of jobs that Ended Not OK	Shows the top 10 Applications with the highest number of jobs failures. The aggregation includes Applications with the same names in different Servers or Sub-Applications. For details of the server and Sub-Application of each Application, see the Applications that had the highest number of jobs that Ended Not OK table.
Applications that had the highest number of jobs that Ended Not OK	Shows the list of Applications with the highest number of job failures. Table limits: Application: 1000 Sub-application: 20 Control-M Server: 2
Top 10 Folders that had the highest number of jobs that Ended Not OK	Shows the top 10 Folders with the highest number of jobs failures. The aggregation includes folders with the same name in different servers. For details of the server of each job, see the Applications that had the highest number of jobs that Ended Not OK table.
Folders that had the highest number of jobs that Ended Not OK	Shows the list of folders with the highest number of job failures. Table limits: Folder: 1000 Control-M Server: 3 Application: 4
Top 10 Hosts that had the highest number of jobs that Ended Not OK	Shows the top 10 Control-M Agents with the highest number of job failures. The aggregation includes hosts with the same name in different servers. For details of each host, see the Hosts that had the highest number of jobs that Ended Not OK table.
Hosts that had the highest number of jobs that Ended Not OK	Shows the list of hosts with the highest number of job failures. Table limits: Host: 1000 Control-M Server: 2 Application: 10

The following examples demonstrate how the Workflow Health dashboard is used to gain additional insights using the available dashboard filters:

Determine which job that belongs to the Application FIN and Sub-application FINCBS failed the most in the last 30 days.
1. From the Time filter, select the Last 30 days.
2. In the Search field, type Application:FIN AND SubApplication:FINCBS.
3. View the jobs that failed the most in the Top 10 Jobs that had the highest number of executions that Ended Not OK panel.
Determine which File Transfer failed most in the last year and the overall robustness of the file and to determine the dates when it failed.
1. From the Time filter, select the Last year.
2. In a new filter, set JobType to File Transfer.
3. In the Top 10 Jobs that had the highest number of executions that Ended Not OK panel, select the job that failed most.
4. In the Executions success rate panel, view the value for this job.

In the Daily executions Ended Not OK panel, view the dates when this File Transfer failed.

Workflow Trends and Peak Volumes Dashboard

The Trends and Peak Volumes dashboard enables you to explore historical volumes trends, peak dates and the applications effecting the peaks dates.

The Trends and Peak Volumes dashboard includes the following panels:

Panel
Total runs	Shows the volume of job runs.
Total executions	Shows the volume of job executions.
Daily jobs runs	Shows the total number of job runs per day, displayed over time. Each point on the graph is an aggregation of the total daily job runs.
Daily jobs executed	Shows the total jobs executed per day, displayed over time. Each point on the graph is an aggregation of the total daily job executed.
Top 10 days that had the highest number of jobs runs	Shows the top 10 days with the highest number of job runs. The aggregation is done by calendar run day and not by Control-M new day.
Top 10 days that had the highest number of jobs executed	Shows the top 10 days with the highest number of job executions. The aggregation is done by calendar execution day and not by Control-M new day.
Top 10 Applications that had the highest number of jobs runs	Shows the top 10 Applications with the highest number of job runs. The aggregation is includes Applications with the same name with different Sub-Applications. For details of the Sub-Applications for each Application, see the Applications that had the highest number of job runs table.
Applications that had the highest number of jobs runs	Shows the list of Applications with the highest number of job runs. The table includes Application general attributes. Table limits: Application: 1000 Sub-Application: 20 Control-M Server: 2
Top 10 Applications that had the highest number of jobs executed	Shows the Applications with the highest number of jobs executed The aggregation includes Applications with the same name in different. If you have Applications with the same name with different Sub-Applications. For details of the Sub-Applications for each Application, see the Applications that had the highest number of jobs executed table.
Applications that had the highest number of jobs executed	Shows the list of Applications with the highest number of job executed. Table limits: Application: 1000 Sub-Application: 20 Control-M Server: 2

The following examples demonstrate how the Workflow Trends and Peak Volumes dashboard is used to gain additional insights using the available dashboard filters:

Determine which day in the last year had the most job executions and which Applications had an impact on that day.
1. From the Time filter, select Last year.
2. Select the busiest day bar in the Top 10 days that had the highest number of jobs executed panel.
3. View which Applications had an impact on that day and their relative share in the Applications with the highest number of jobs executed table, such as determining which day in the last year had the most job executions and which Applications had an impact on that day.

Determine which Application in the last 7 days had the most File Transfers, and the relative share of each Sub-Application of the total File Transfers.
1. From the Time filter, select the Last 7 days.
2. In a new filter, select the Index Pattern named ctm_job_executions, then set JobType to File Transfer.
3. In the Top 10 days that had the highest number of jobs executed panel, select the Application with the highest number of File Transfers.
4. In the Applications that had the highest number of jobs executed panel, view the File Transfers of each Sub-application.

Workflow Distribution Dashboard

The Workflow Distribution dashboard enables you to monitor the workflow and job distributions in the system to ensure effective load balancing and Agent utilization.

The Workflow Distribution dashboard includes the following panels:

Panel	Description
Number of Jobs executed by Control-M Server	Shows the number of jobs executed by a Control-M/Server.
Daily Jobs executed by Control-M Server	Shows the total number of jobs executed each day by a Control-M/Server. The graph includes a line for each Control-M Server. Every point on each line is the aggregation of total jobs executed each day by a Control-M Server.
Top 10 Hosts that had the highest number of Jobs executed	Shows the top 10 Control-M/Agents with the highest number of job executions.
Hosts that had the highest number of Jobs executed	Shows the Control-M/Agents with the highest number of job executions. Table limits: Host: 6000 Control-M Server: 1 Job Type: 5
Top 5 Hosts that had the highest number of Jobs executed, daily trend	Shows the top 5 Control-M/Agents with the highest number of daily job executions. The graph includes a line per Control-M/Agent. Every point on each line is the aggregation of total jobs executed each day by a Control-M/Agent.
Daily Job Types executed	Shows the daily total number of jobs executed based on job type. The graph includes a line per job type. Every point on each line is the aggregation of total jobs executed each day based on job type.
Job Types distribution	Shows the total number of job executed by job type and their overall percentage from all job executions.

The following examples demonstrate how the Workflow Distribution dashboard is used to gain additional insights using the available dashboard filters:

Determine which are the most loaded Control-M/Agents that serve ReatilBanking Application and their usage trend in the last 90 days from both volume and job types.
1. From the Time filter, select the Last 90 days.
2. Add the filter Application is ReatilBanking.
3. View the most loaded Control-M/Agents that serve ReatilBanking Application and their usage trend in the Top 5 Hosts that had the highest number of Jobs executed, daily trend panel.

Determine which are the most loaded Control-M/Agents that serve ReatilBanking Application and their usage trend in the last 90 days from both volume and job types.
1. From the Time filter, select the Last 30 days.
2. In the Search field, type: Application:PrivateBanking AND SubApplication:EMEA AND JobType:SAP
3. In the Hosts that had the highest number of Jobs executed panel, view the load on all the Control-M/Agents.

Workflow Alerts Dashboard

The Workflow Alerts dashboard enables you to ensure workflow and job efficiency; an Alert is a clear indication that something went wrong.

The Workflow Alerts dashboard includes the following panels:

Panel	Description
Total number of Job Alerts	Shows the volume of job Alerts.
Daily Alerts - Opened vs Closed	Shows the daily job Alerts opened and daily job Alerts closed. Every point on the relevant line is the aggregation of total Alerts opened or closed per the relevant day and time.
Most common Alert messages	Shows the most common Alert messages. Table limits: 12,000 Messages
Top 10 Jobs that generated the highest number of Alerts	Shows the top 10 jobs that generated the highest number of Alerts. The aggregation includes jobs with the same name in different Servers, Folders, Applications or Sub-Applications. For details of the server, folder, Application and Sub-Application of each job, see the Jobs that generated the highest number of Alerts table.
Jobs that generated the highest number of Alerts	Shows the list of jobs with the highest number of Alerts. Table limits: Job Name: 7,000 Application: 2 Sub-Application: 2 Control-M Server: 1
Top 10 Applications that generated the highest number of Alerts	Shows the top 10 Applications with the highest number of Alerts. The aggregation includes Applications with the same name in different Sub-applications or Servers. For details of the server and Sub-Application of each Application, see the Applications that generated the highest number of Alerts table.
Applications that generated the highest number of Alerts	Shows the list of Applications with the highest number of Job Alerts. Table limits: Application: 1,000 Sub-Application: 20 Control-M Server: 2
Top 10 Hosts that generated the highest number of Alerts	Shows the top 10 Control-M/Agents with the highest number of jobs Alerts. The aggregation includes hosts with the same name in different Control-M/Servers. for details of the servers of each host, see the Hosts that generated the highest number of Alerts table.
Hosts that generated the highest number of Alerts	Shows the list of Control-M/Agents with the highest number of job Alerts. Table limits: Host: 12,000 Control-M Server: 1

The following examples demonstrate how the Workflow Alerts dashboard is used to gain additional insights using the available dashboard filters:

Determine which jobs generated the highest number of Alerts in the PrivateBanking Application in the AP Sub-Application in the last 30 days and the most common Alert message during that period.

From the Time filter, select the Last 30 days.
In the Search field, type Application:PrivateBanking AND SubApplication:AP.
View the Jobs that generated the highest number of Alerts panel.
View the Most common Alert messages panel.

Workflow Definition Updates Dashboard

The Workflow Definition Updates dashboard enables you to monitor workflow definitions change volumes and sources to understand if they are impacting workflow health.

The Workflow Definition Updates dashboard includes the following panels:

Panel	Description
Total definition updates	Shows the volume of all definition changes, such as definition added, modified, or deleted.
Total definitions added	Shows the volume of all definitions added.
Total definitions modified	Shows the volume of all definitions modified.
Total definitions deleted	Shows the volume of all definitions deleted.
Daily definitions added/p>	Shows the total definitions added per day. Every point on the graph is an aggregation of total daily definition added.
Definitions added	Shows the list of definitions that were added. The table includes the added definitions general attributes and the user who checked in the change. Table limits: Job Name: 1,000 Control-M Server: 3 Folders: 4 Application: 1 Sub-Application: 1 Type: 1 Added By: 1
Daily definitions modified	Shows the total definitions modified per day. Every point on the graph is an aggregation of total daily definition modified.
Definitions modified	Shows the list of the definitions that were modified. Table limits: Job Name: 1,000 Control-M Server: 3 Folders: 4 Application: 1 Sub-Application: 1 Type: 1 Modified By: 3
Daily definitions deleted	Shows the total definitions deleted per day. Every point on the graph is an aggregation of total daily definition deleted.
Definitions deleted	Shows the list of the definitions that were deleted. The table includes the deleted definitions general attributes and the user who checked in the change. Table limits: Job Name: 1,000 Control-M Server: 3 Folders: 4 Application: 1 Sub-Application: 1 Type: 1 Deleted By: 1
Top 10 Applications that had the highest number of updates	Shows the top 10 Applications with the highest number of definition changes. The aggregation is done by Application name, such as if you have jobs with the same Application names in different Sub-applications or Control-M Servers, these are aggregated together. You can see the breakdown in the Applications that had the highest number of updates table
Applications that had the highest number of updates	Shows the list of Applications with the highest number of updates. Table limits: Application: 500 Sub-Application: 10 Control-M Server: 2 Update Type: 3
Top 10 Folders that had the highest number of updates	Shows the top 10 folders with the highest number of related definition changes. The aggregation includes folders with the same name in different servers, Applications, or Sub-Applications. For details of the server, Application, and Sub-Application of each folder, see the Folders that had the highest number of updates table
Folders that had the highest number of updates	Shows the list of folders with the highest number of related definition changes. Table limits: Folder: 2,000 Control-M Server: 3 Update Type: 3

The following examples demonstrate how the Definition Updates dashboard is used to gain additional insights using the available dashboard filters:

A developer received a ticket that the sendRun job that belongs to the RetailBanking Application failed yesterday August 18th. The ticket sender wants to know if the job definitions of this job were changed recently.
1. From the Time filter, select the Last 7 days.
2. In a new Filter, set Application to RetailBanking, and setJobName to sendRun.
3. In the Definitions Modified panel, view if the the job was modified and if so then by which user.
4. In the Daily definitions modified panel, view which day the definitions where modified.

A developer received a ticket that the sendRun job that belongs to the RetailBanking Application failed yesterday August 18th. The ticket sender wants to know if the job definitions of this job were changed in the last week to the RetailBanking Application.
1. From the Time filter, select the Last 7 days.
2. In a new filter, set Application to RetailBanking.
3. In the Definitions Modified panel, view if any jobs in the RetailBanking Application were modified.
4. In the Daily definitions modified panel, view which day the definitions were modified.

SLA Management Services Dashboard

The Workflow SLA Management Services dashboard enables you to ensure the health and robustness of the critical Control-M business SLA Services, and enables you to reduce critical SLA Service durations, which improves the business efficiency of these Services.

The Workflow SLA Management Services dashboard includes the following panels:

Panel	Description
Services success rate	Shows the total SLA Management Services executions ended on time/Total SLA Management services executions. The Service success rate rounds up to 100% when failures are less than 0.0001 of successes.
Total Services executions	Shows the volume of Services executions.
Total Services Ended OK	Shows the volume of Services executions ended on time.
Total Services Ended Late	Shows the volume of Services executions that passed their defined SLA deadline.
Top 10 Services that had the highest number of executions that passed their SLA deadline	Shows the top 10 Services with the highest number of executions that were late. For details of the size of the delay (the Avg Slack time) in minutes for each Service see the Services that had the highest number of executions that passed their SLA deadline table.
Services that had the highest number of executions that passed their SLA deadline	Shows the list of SLA Services with the highest number of executions that passed the SLA deadline with the average delay in minutes. Table limits: 12,000 Service Names
Top 10 Services that had the highest risk of passing their SLA deadline (minimum average Slack time)	Shows the top 10 Services with the highest risk of passing their SLA deadline (minimum average Slack time).
Services that had the highest risk of passing their SLA deadline (minimum average Slack time)	Shows a list of Services with the highest risk of passing the SLA deadline, the number of executions for these services, and their average Slack time. Table limits: 12,000 Service Names
Top 5 Services that had the highest risk to pass their SLA deadline, daily trend	Shows the top 5 services with the highest risk of passing their SLA deadline, daily trend. The graph includes a line per SLA Management Service. Every point on each line is the daily Average Slack time for the relevant Service execution.
Top 5 Services that had the longest average duration, daily trend	Shows the daily average Service duration trend for the top 5 Services with the longest average duration. The graph includes a line per SLA Management Service. Every point on each line is the daily average Service duration time for the relevant Service execution.
Top 10 Service Jobs that had the highest number of executions that Ended Not OK	Shows the top 10 jobs with the highest number of executions that Ended Not OK. The aggregation includes jobs with the same name in different servers, folders, Applications, or Sub-Applications. For details of the servers, folders Application, or Sub-Applications of each job, see Service Jobs that had the highest number of executions that Ended Not OK table.
Service Jobs that had the highest number of executions that Ended Not OK	Shows a list of the jobs that are part of an SLA Service with the highest number of executions that Ended Not OK. Table limits: Job Name: 1,000 Control-M Server: 3 Folder: 4 Service Name: 3 Application: 1 Sub-Application:1 Host:1
Top 10 longest Jobs affecting Service critical path completion	Shows the top 10 jobs with the longest average duration that affected the Service critical path completion. The aggregation includes jobs with the same name in different servers, folders, Applications, or Sub-Applications. For details of servers, folders, Applications, or Sub-Applications of each job see the Longest Jobs affecting Service critical path completion table.
Longest Jobs affecting Service critical path completion	Shows a list of the jobs with the longest average duration that affected the Service critical path completion. Table limits: Job Name: 2,000 Control-M Server: 3 Folder: 4 Service Name: 2 Application: 1 Sub-Application:1 Host:1
Top 10 Jobs that had the longest time Gaps affecting Service critical path completion	Shows the top 10 Jobs with the longest time gap that affected the Service critical path completion. The aggregation is done by Job name, such as if you have jobs with the same names in different Servers, Folders, Applications or Sub-applications, these are aggregated together. You can see the breakdown in the Jobs that had the longest time Gaps affecting Service critical path completion table.
Jobs that had the longest time Gaps affecting Service critical path completion	Shows a list of jobs with the longest time gap that affected the Service critical path completion. Job after gap table limits: Job Name after gap: 1,000 After Job - Folder: 4 After Job - Server: 3 After Job - Application: 1 After Job - Sub-application: 1 After Job - Host: 1 Service Name: 3 Job before gap table limits: Job Name before gap: 1 Before Job - Folder: 1 Before Job - Server: 1 Before Job - Application: 1 Before Job - Sub-Application: 1 Before Job - Host: 1

The following examples demonstrate how the SLA Management Services dashboard is used to gain additional insights using the available dashboard filters:

Determine what the duration trend of the PrivateBanking Service is and which jobs in this Service failed most in the last 3 months.
1. From the Time filter, select the Last 3 months.
2. In a new Filter, set ServiceName to PrivateBanking.
3. In the Top 5 Services that had the longest average duration, daily trend panel, view the PrivateBanking Service duration trend.
4. In the Service Jobs that had the highest number of executions that Ended Not OK panel, view the list of jobs that in the PrivateBanking SLA Service that failed most.

Determine how to reduce completion time of RetailBanking Service as compared to the the last 30 days.
1. From the Time filter, select the Last 30 days.
2. In a new filter, set ServiceName to RetailBanking.
3. In the Top 10 longest Jobs affecting Service critical path completion panel, view the top 10 jobs in the critical path of RetailBanking that have the longest average duration.
4. In the Top 10 Jobs that had the longest time Gaps affecting Service critical path completion panel, view the top 10 jobs in the critical path of RetailBanking that waited most to start executing even though their predecessor jobs were finished. With this information, try to have these jobs start with less wait.

Optimization Insights Dashboard

The Optimization Insights dashboard enables you to reduce cost and operation inefficiency in Control-M, and to review edge cases that might affect Control-M components performance or Workflow efficiency.

The Optimization Insights dashboard includes the following panels:

Panel	Description
Total Dummy executions	Shows the volume of Dummy job types or jobs that are set to Run As Dummy executions.
Daily Dummy executions	Shows the total Dummy executions per day, trend. Every point on the graph is aggregation of total daily Dummy executions.
Top 10 Dummy Jobs that had the highest number of executions	Shows the top 10 Dummy or Run As Dummy jobs that executed most. The aggregation is done by Job name, such as if you have jobs with the same names in different Servers, Folders, Applications or Sub-applications these are aggregated together. You can see the breakdown in the Dummy Jobs that had the highest number of executions table.
Dummy Jobs that had the highest number of executions	Shows the list of Dummy jobs that executed most. Table limits: Job Name: 1000 Control-M Server: 3 Folder: 4 Application: 1 Sub-Application:1
Top 10 Hosts that executed the lowest number of Jobs	Shows the Control-M/Agents with the lowest number of job executions.
Top 10 Hosts that executed the highest number of Jobs	Shows the Control-M/Agents with the highest number of job executions.
Hosts that executed the highest number of Jobs	Shows the list of the Control-M/Agents with the highest number of job executions. Table limits: Host: 6000 Control-M Server: 1 Job Type: 5
Top 10 non Cyclic Jobs that had the highest number of Reruns	Shows the top 10 non cyclic jobs with the highest number of reruns. z/OS jobs only appear on this table from the second rerun.
Non Cyclic Jobs that had the highest number of Reruns	Shows the list of non cyclic jobs with the highest number of reruns. z/OS jobs only appear on this table from the second rerun. Table limits: Job Name: 1000 Control-M Server: 3 Folder: 4 Application: 1 Sub-Application:1 Job Type:1 Host: 1
Top 10 Jobs that had the longest average duration	Shows the jobs with the longest average duration. The aggregation includes jobs with the same name in different servers, folders, Applications or Sub-Applications. For details of the servers, folders, Applications, or Sub-Applications for each job see the Jobs that had the longest average duration table.
Jobs that had the longest average duration	Shows the list of jobs with the longest average duration. Table limits: Job Name: 1000 Control-M Server: 3 Folder: 4 Application: 1 Sub-Application:1 Job Type:1 Host: 1

The following examples demonstrate how the Optimization Insights dashboard is used to gain additional insights using the available dashboard filters:

Determine which Control-M/Agents had minimal usage in the last year that can be replaced with Remote Host components.
1. From the Time filter select the Last year.
2. View the Control-M/Agents with the least amount of executed jobs in the Top 10 Hosts that executed the lowest number of Jobs panel.
3. Select the Control-M/Agents with the least amount of executed jobs and view the associated job types in the Hosts that executed the highest number of Jobs panel.
4. If the Control-M/Agents only executed OS job types, you might be able to replace them with Remote Hosts.

Determine which File transfers jobs took the longest time to transfer and are part of the PrivateBanking Application and EMEA Sub-application in the last 30 days.
1. From the Time filter, select the Last 30 days.
2. In the Search field type Application:PrivateBanking AND SubApplication:EMEA AND JobType:File Transfer
3. View which File transfers jobs took the longest time to complete in the Jobs that had the longest average duration panel.

Job Execution Dashboard

The Job Execution dashboard enables you to ensure job execution efficiency and duration stability.

The Job Execution dashboard includes the following panels:

Panel	Description
Total executions	Shows the volume of job executions.
Average Job duration (Minutes)	Shows the average duration in minutes of all the jobs that were executed in the selected time frame and filters.
Jobs that had the highest number of executions	Shows the list of jobs that were executed most together with their average duration statistics. Table limits: Job Name: 1,000 Control-M Server: 3 Folders: 4 Application: 1 Sub-Application: 1 Job Type: 1 Host: 1
Top 5 Jobs that had the longest average duration, daily trend	Shows the daily average jobs duration trend for the top 5 jobs with the longest average duration. The graph includes a line per job. Every point on each line is the daily average job duration time for the relevant job executions.
Number of Jobs started by the hour (hour is in UTC time zone)	Shows the number of jobs that started to execute by hour of day. The number of jobs executed on a specific hour represent all the jobs that started to execute between that hour and the next hour. If job1 started to execute in 9:01 and job2 started in 9:59, the 9:00 bar shows 2 jobs because between 9:00 and 10:00, 2 jobs started to execute. The jobs starting hour is appears in UTC time zone (all other panels show time in your current browser time zone).
Number of Jobs ended by hour (hour is in UTC time zone)	Shows the number of jobs that ended execution by hour of day. The number of jobs executed during a specific hour represent all the jobs that finished executing between that hour and the next hour. If job 1 finished executing at 9:01 and job 2 finished at 9:59, the 9:00 bar shows 2 jobs, because between 9:00 and 10:00, 2 jobs finished executing. The jobs ending hour appears in UTC time zone (all other panels show time in your current browser time zone)
Top 10 Cyclic Jobs that had the highest number of Reruns	Shows the top 10 cyclic jobs with the highest number of reruns. The aggregation includes jobs with the same names in different Servers, Folders, Applications or Sub-applications. z/OS jobs only appear on this table from the second rerun.
Cyclic Jobs that had the highest number of Reruns	Shows the list of cyclic jobs with the highest number of reruns. z/OS jobs only appear on this table from the second rerun. Table limits: Job Name: 1,000 Control-M Server: 3 Folders: 4 Application: 1 Sub-application: 1 Job Type: 1 Host: 1
Monthly Jobs executed	Shows the volume of job executed per month.

The following examples demonstrate how the Job Execution dashboard is used to gain additional insights using the available dashboard filters:

Determine which jobs have the longest average duration in the RetailBanking Application in the last 4 months and if the jobs have any duration degradation over time.
1. From the Time filter select the Last 4 months.
2. Add the filter Application is RetailBanking.
3. View which jobs have the longest average duration and if the jobs have any duration degradation over time in the Top 5 Jobs that had the longest average duration, daily trend panel.
PrivateBanking users opened a ticket that they experienced a lag in the jobs executions on August 18 between 10:00 to 14:00.
1. From the Time filter, select August 18 from 00:00 to 23:30.
2. Add the filter Application is PrivateBanking.
3. View the load of jobs between 10:00 to 14:00 in the Number of Jobs started by hour and Number of Jobs ending by hour panels.
A ticket states that the sendRun job that belongs to the RetailBanking Application failed on August 18th. You need to compare the failed job duration to the previous successful runs in the previous week.
1. From the Time filter, select August 11 to August 18.
2. Add the filter Application is RetailBanking and JobName is sendRun.
3. View sendRun duration trend in that peiod in the Top 5 Jobs that had the longest average duration, daily trend panel.

User Actions Dashboard

Configuring Workflow Insights

This procedure describes how to configure the Workflow Insights settings.

Before You Begin

Verify that you have Full Database Maintenance privilege in CCM.

Begin

From the Configuration domain, click and then select Workflow Insights Details and Settings.
Click Settings and define the parameters, as follows:
- Retain Workflow Insights data for X months: Determines the number of months the Workflow Insights data is available.
  - Valid Values: 3 - 60
  - Default: 16
  If you increase the data retention period, you might need to upgrade the Control-M/EM distributed instances. For more information, contact Customer Support.
- Customer backup location: Determines the network location where Elastic cluster data snapshots is backed up.
  - By setting this parameter, you enable data backup of the Elastic cluster.
  - Use a network location that is accessible from all Control-M/EM distributed instances.
  - For Windows, Control-M/EM distributed components run with system account privileges. Either allow system account access to the share location or change the Configuration Agent (CA) service log on to a user with access rights.
  - Before setting the backup location, mount the file system to the same location for all Control-M/EM distributed instances.
Recycle all Elastic Search instances and then recycle all Workflow Insights services as described in Recycling a Component.
Verify that you defined the Workflow Insights Backups, as described in Defining Workflow Insights Backups.