Top Running Reports
Using this report, you can list the reports that have been running for long periods of time or that have run an excessive number of times. A report will be listed as Top Running, based on its overall cost to the system, determined by the average execution time * run count. By default, the most costly reports are listed first. Note that the average execution time includes not only the database query, but also the time associated with building the report on the Portal server.
Explore your data center using APTARE customizable report templates or by using parts of your IT infrastructure as entry points. Use Search to find reports, templates and dashboards across the portal.
Use the Reports tab to examine the catalog of templates, dashboards and reports - organized by products along with user-created, and system folders. This report is located here:
System Administration Reports > Top Running Reports
Select the time range for the list in the scope selector.
Click the
Run Count link to view
Top Running Reports.
Template Name | The report template name. |
Report Name | The name of the saved report instance. |
Is Drilldown | Indicates if the report is a drilldown from a parent report. |
Last Run By | The login name of the user who last ran the report. |
Run Count | Total number of times the report was run. |
Max Execution Time | The maximum amount of time the report has taken to run. |
Avg Execution Time | The average amount of time the report has taken to run. |
Max DB Time | The maximum amount of time used to access the Portal database. |
Avg DB Time | The average amount of time used to access the Portal database. |
Last Run Time | The date and time the report was last run during this time period. |
First Run Time | The date and time the report was last run during this time period. |
Dashboard Considerations
A dashboard that contains four different reports (portlets) will appear in this Top Running Reports list as four separate records. This summary does not display a row for the high-level dashboard, just the reports contained within the dashboard.
• If the portlet within the dashboard is a saved report, the name of the saved report will be displayed in the Report Name column.
• If the portlet is not a saved report—that is, it was simply generated and dragged into the dashboard—then Dashboard Report will be displayed in the Report Name column.
Top Running Report Details
The Run Count in the Top Running Reports Summary provides access to the list of reports that have consumed higher than average resources. Use this list to determine if any actions need to be taken. For example:
• Adjust the scope of the report to narrow the content.
• Schedule certain top running reports to be run at off hours.
• Verify that automatically schedule reports are scheduled appropriately and are not running more frequently than is required.
• Consider scheduling frequently run reports to run once, with filesystem exports or emails to users.
Template Name | The report template name. |
Report Name | The name of the saved report instance. |
Is Drilldown | Indicates if the report is a drilldown from a parent report. |
Dashboard Name | Name of the dashboard in which this report is located. |
Schedule Name | The name attached to the schedule for the report. |
Schedule Frequency | The schedule frequency. Click the frequency information to edit and save the new schedule. You can also delete the schedule. |
LDAP ID | The LDAP ID of the user running the report. |
Total Execution Time | The total amount of time the report took to render. |
DB Execution Time | The total amount of time used for Portal database access. |
Run Time | The transaction timestamp for the report. |