The section includes the following topics:
Report Manager provides pre-defined reports divided into the following report sets:
Profile reports set. These reports provide information about the top n consumers of your application and thus enables you to pinpoint tuning opportunities.
A new subset of the Profile reports set is the Geographical reports. |
These profile reports provide information about the top n consumers of your application, based on where they are located geographically; whether a state or city in the U.S.A., or a country shown on a two-dimensional world map. These graphic reports enable you to pinpoint tuning opportunities by geographic region.
All the reports are arranged according to the hierarchy of the Tier as shown in the following general example:
Reports of a Tier-level, for example, provide a performance comparison between the various Tiers of your application. These reports can contain data of several Tiers, for example, Cross-Tiers Availability reports.
Reports of an Instance-level provide information about the complete instance that is the whole system, such as a Web Server, an Oracle Instance, or a Java Virtual Machine.
The structure of each report, in general, contains the following sections:
Report Manager generates all the reports and displays them in PDF format, which enables you to navigate within the report using bookmarks (Navigation pane) on the left and links.
There are two types of links: internal links and launching links. For example, the Heat Matrix contains internal links, which you can click to display its detailed information in the report. The launching links enable you to launch the relevant Precise or Insight product - for further investigation - in context with the information displayed in the report page (same entity, Time Frame, etc.).
You can save a copy of a report in your file system and display them later using Adobe Acrobat Reader. |
Launching links are available only for reports where this option is enabled. To launch a Precise or Insight product, click the link on the upper right-hand corner of the window. See Setting the General settings.
The Profile reports provide information about the top n consumers of the application. The consumers can be either Entities such as programs and users, or Instances such as JVMs, SAP Systems, and Oracle Instances.
Using the Profile reports, you can focus on the hot spots, where performance improvement probably can be most effective for the overall behavior of your application.
For each Profile report, Report Manager calculates the top n consumers based on counters, such as In MS-SQL Times and Sessions. You can select the counters by which Report Manager calculates the top n consumers through the Standard profile report - general tab of the report properties dialog box. Each type of report may include a different list of counters.
For each Tier, Report Manager provides the following report types:
The Instance-level report provides a comparison between the top n instances and displays over time information for each one of the top n instances.
The Entity-level report provides a comparison between the top n entities of each instance in the Tier-level. (This comparison applies in case you chose the Same entity option for the Consider Identically Named Entities in Different Instances property in the Standard profile report - general tab.)
The Profile report set includes reports that have similar structure and properties (standard reports). In addition, the Profile reports set includes reports that have different structures and properties.
The standard Profile report structure consists of the following sections:
The following information is displayed:
The opening page of the Profile report is similar to all the pre-defined reports except that the summary section provides information related to the specific report as follows:
The Summary Heat Matrix indicates, in a tabular format, the top instances with the most consuming entities for each of the reported counters. Each row of the table specifies an instance, and each column specifies a counter. The cell color-code and the left number, in each column, indicates the rank (order in the top n) of the instance for the specific counter. The right number specifies the normal rank, based on its baseline (for instances with no baseline, a dash sign is displayed instead of the right number).
From this page, you can determine which instance you should start to investigate. Normally, you would choose the instance with the highest value for a selected counter. However, the value of the selected counter for the entire instance does not always point to the significance of the top n consumers. Therefore, the instances are ranked by the combined counter value of the top n consumers, and not by the counter value of the entire instance. For example, in an application that runs two instances, HR and CRM, the top-10 users of the HR instance consume 800 hours out of 1,000 hours of the entire HR instance. The top-10 users of the CRM instance consume 500 hours out of 2,000 hours of the entire CRM instance. Even though the CRM instance consumes more than the HR instance, the CRM instance will be ranked the second, while the HR instance will be the first.
The Summary Heat Matrix applies only if the report meets all the following conditions:
The Entity Heat Matrix page indicates, in a tabular format, the main consumers of each reported counter. For Instance-level reports, a single Heat Matrix is displayed. For Entity-level reports, an Entity Heat Matrix is displayed for each instance.
Each row of the table specifies an entity, and each column specifies a counter. The cell color-code and the left number, in each column, indicates the rank (order in the top n) of the entity for the specific counter. The right number specifies the normal rank, based on its baseline (for entities with no baseline, a dash sign is displayed instead of the right number).
From this page, you should choose the entity with the highest rank. Each entity name links to the Entity Overtime Behavior graphs.
The Entity Mapping Table is displayed in reports whose entity names are too long to display in the detailed information pages. Report Manager generates the Entity Mapping Table only for the Statements reports, such as Oracle or SQL Server Profile Report - Statements and SQL Server Profile Report - Ad-hoc Batches.
In these reports, the detailed information pages display the statement IDs instead of the Statement Text (also a link to the Entity Mapping Table). See About the Profile report - overtime graphs.
You can specify the maximum number of characters in the Statement Text. |
Report Manager generates a set of Comparison graphs for each of the reported counters. These graphs compare the top n entities of the counter. Instance-level reports have a single set of Comparison graphs for each counter, and Entity-level reports have a set of Comparison graphs for each instance.
Each graph includes a color coded legend. In addition, the legend below the graphs is common to all graphs in the page. This legend maps the number specified in the x-axis of the graph to the entity name (this number is the entity rank). You can click the entity name to display the Entity Overtime Behavior graphs.
Although an entity may be displayed in the Heat Matrix, it is omitted in the comparison charts of counters that are not part of their top n consumers. |
Report Manager generates Behavior Overtime graphs for each of the reported entities. Unlike the comparison graphs, all reported entities have the same graph set, regardless of the entities consumption.
The Behavior Overtime graphs contain a launching link to the related Precise or Insight product. You can click the launching link for further investigation in context of the displayed entity. In addition, if the entity name is too long, such as in the Statements report, a link to the Statement Text (Mapping Table) is available.
The Properties dialog box for standard Profile reports contains properties that are specific to the selected report. In general, the properties are similar for all the standard Profile reports. However, you may find some differences according to the relevancy of the property to the report.
The Properties dialog box contains three tabs in which you can set the properties:
In addition to these three tabs, the Description tab displays a textual description of the report structure and contents.
The General tab contains the following properties:
To set Profile report properties - general tab
The Time Frame tab contains the following properties:
To set Profile report properties - time frame tab
The Filters tab contains the following properties:
To set Profile report properties - filters tab
The Application Profile report is a Cross-Tiers report that provides information related to all the installed Tiers in the application. The Tiers are compared in terms of total time, average execution time, and the number of executions.
About the Application Profile report structure
The Application Profile report structure consists of the following sections:
The summary section provides the number of installed Tiers in the application.
The Tier Comparison graphs display summarized values and baselines of the Total Time, Average Time, and Executions for all the Tiers installed in the application.
Report Manager generates a Cross-Tiers Behavior Overtime graph for each counter. The counters include the Total Time, Average Time, and Number of Executions. These graphs provide a behavior comparison over time between all installed Tiers.
Report Manager generates a Behavior Overtime graph for each installed Tier and each counter within the Tier. The counters include the Total Time, Average Time, and Number of Executions. Each graph also contains the counter baseline.
The Properties dialog box of the Application Profile report contains one tab in which you can set the time frame properties, as follows:
In addition, there is a Description tab which displays a textual description of the report structure and contents.
To set Application Profile report properties - time frame tab
Report Manager only generates the Response Time report for SAP Tier (client-side technologies). This report provides information about the response times of your system.
For the SAP Tier, the graph displays for each response time the percentage of SAP transactions accordingly that have a lower response time than a maximum value specified in the report properties - Response time report (general tab).
The Response Time report structure consists of the following sections:
The summary section provides the number of instances included in the report.
Report Manager generates a Response Time Distribution graph for each instance running in the Tier. The graph displays a bar for each response time step. Each bar indicates the cumulative percentage and the actual number of executions (SAP transactions in the SAP Tier) that their response time is less or equal to the response time step.
Executions of which the response time is greater than the specified maximal value, are not included in the graph, and therefore the percentage of the total executions may not add up to 100 percent.
The Properties dialog box contains three tabs in which you can set the Response Time report properties:
In addition to these three tabs, there is a Description tab which displays a textual description of the report structure and contents.
The General tab contains the following properties:
To set Response time report properties - general tab
The Time Frame tab contains the following properties:
To set Response time report properties - time frame tab
The Filters tab contains the following property:
To set Response time report properties - filters tab
Report Manager only generates the Schema Changes report for Oracle and SQL Server Tiers (database technologies). This report displays a chronological log of all changes in the database schema and definition in a tabular format. You can use this report to identify the relations between changes in the database schema and definition to trends in database performance.
To generate this report, Report Manager compares the status of the database at two points in time. Therefore, changes made after the first point in time of which the effect does not remain till the second point in time, will not be shown in the report. For example, a table that was created after the first point in time but was dropped before the second point in time will not appear in the report.
The Schema Changes report structure consists of the following sections:
For the SQL Server Tier, the report only displays the schema changes. The database definition changes are displayed in a separate report named Database Definition Changes. |
The summary section provides the total number of changes detected in the report period.
For the Oracle Tier, the Database Definition Changes Table is part of the Schema Changes report, and the report displays a table for each instance.
For the SQL Server Tier, the Database Definition Changes Table is displayed in a separate report named Database Definition Changes, and the report displays a table for each instance and database.
For the Oracle Tier, the report displays a table for each instance. For the SQL Server Tier, the report displays a table for each instance and database.
The Properties dialog box contains two tabs in which you can set the Schema Changes report properties:
In addition to these tabs, there is a Description tab which displays a textual description of the report structure and contents.
The Time Frame tab contains the following property:
To set Schema Changes report properties - time frame tab
The Filters tab contains the following properties:
To set Schema Changes report properties - filters tab
The Exception reports provide information about any substantial consumption deviating from the normal behavior. This information assists you with maintaining your application well-tuned.
For each Tier, Report Manager provides the following Exception report types:
The counters set may be different for each Tier. In addition, the counters may be different between the various reports in the same Tier. You can set the counters for each report.
For each report, you can set a threshold. When an entity counter consumption deviates from its baseline by more than the threshold, the exception is reported. You can specify up to two thresholds that will escalate the exception severity level.
You can define filters to eliminate negligible exceptions. Two filter types are available, an absolute filter, which defines a minimal total consumption of an entity over the period, and a relative filter, which defines a minimal consumption percentage of an entity from its instance's total consumption.
When Report Manager generates an Exception report, it also sends an alert to Alerts. Likewise, when working in Alerts, you can drill down to the relevant Exception report from the Alerts user interface. For more information, see the Precise Alerts User's Guide.
The Exception reports set includes reports that have similar structure and properties (standard reports) described in the following topics:
In addition, the Exception reports set includes a report named Unused objects report that has different structure and properties.
The standard Exception report consists of the following sections:
An instance for a standard Exception report displays the following tables:
The following information is displayed for each entity:
The opening page of the Exception report is similar to all the pre-defined reports except that the summary section provides information related to the specific report as follows:
The Summary Heat Matrix indicates, in a tabular format, the top instances with the most severe exceptions for each of the reported counters. It summarizes the number of deviating entities that are detected and their severity level.
In Entity-level reports, each row in the Summary Heat Matrix represents a different instance. Each column represents a different counter. The cell color indicates the average deviation severity of all the reported entities of the instance. The number in the cell indicates the number of entities having exceptions. The instance name is a link to the Related Entity Heat Matrix.
In Instance-level reports, the Summary Heat Matrix displays a single row that indicates the average deviation severity and exceptions number in the entire Tier. (This also applies if you chose the Same entity option for the Consider Identically Named Entities in Different Instances property in the Standard exception report - general tab.)
The Entity Heat Matrix page indicates, in a tabular format, the most problematic entities that have the most significant deviations. Each row in the Entity Heat Matrix represents a different entity. Each column represents a different counter. The cell color indicates the severity of the counter deviation from its normal behavior (baseline). The entity name is a link to the Entity Overtime Behavior graphs.
The New Entities Table lists new entities in the current instance (or Tier in Instance-level reports), which met the report filtering criteria of the minimal consumption amount. Entities are considered new if the Performance Management Database did not calculate a baseline for the entity yet.
For each new entity the table displays its total time value and the percentage that its total time occupies from the entire instance consumption (or Tier consumption in case of Instance-level reports).
The Entity Mapping Table is displayed in reports whose entity names are too long to display in the detailed information pages. Report Manager only generates the Entity Mapping Table for Statements reports, such as the Oracle or SQL Server Exception Report - Statements and the Oracle or SQL Server Exception Report - Ad-hoc Batches.
In these reports, the detailed information pages display the statement IDs instead of the Statement Text (also a link to the Entity Mapping Table). See About the Exception report - summary table and overtime graphs.
Report Manager generates an Exception Summary Table and Behavior Overtime graphs for each of the reported entities. Each row in the Exception Summary Table includes a deviated counter, with its most recent exception details, including: the Exception Time, the Actual Counter Value, its Baseline Value, and the Percent of Change.
Following the Exception Summary Table, a set of Overtime graphs is displayed, one for each counter. Each graph displays the Actual Counter Behavior, the Counter Baseline, and the Exception Threshold.
This page contains a launching link to the related Precise or Insight product. You can click the launching link for further investigation in context of the displayed entity. In addition, if the entity name is too long, such as in the Statements report, a link to the Statement Text (Mapping Table) is available.
The Properties dialog box for Standard Exception reports contains properties that are specific to the selected report. In general, the properties are similar for all the Standard Exception reports. However, you may find some differences according to the relevancy of the property to the report.
The Properties dialog box contains three tabs in which you can set the properties:
In addition to these three tabs, there is a Description tab which displays a textual description of the report structure and contents.
The General tab contains the following properties:
To set Exception report properties - general tab
The Time Frame tab contains the following properties:
To set Exception report properties - time frame tab
The Filters tab contains the following properties:
To set Exception report properties - filters tab
This report is applicable for database technologies, such as Oracle and SQL Server. The report lists the objects that were not used during the specified time frame of the report. You can use this report to identify cases such as forgotten tables and redundant indices. These cases are frequent in data warehouse applications, which may contain tables and clusters that are not accessed by statements. By dropping these unused objects, you can free disk space without affecting the database performance.
The unused objects report structure consists of the following sections:
The summary section provides the number of unused objects in the report.
Report Manager generates tables of unused objects as follows:
The table lists all the unused objects detected during the report period, their owner, and their type.
The Properties dialog box contains two tabs in which you can set the Unused Objects report properties:
In addition to these tabs, there is a Description tab which displays a textual description of the report structure and contents.
The Time Frame tab contains the following property:
To set Unused Objects report properties - time frame tab
The Filters tab contains the following properties:
To set Unused Objects report properties - filters tab
The Availability reports provide information about failure and downtime of Tiers in your application. For most Tiers, Report Manager tracks only the Instance availability. However, for some Tiers, such as SAP and SQL Server, Report Manager also tracks the availability of other entities.
Report Manager provides the following Availability report types:
The availability percentage calculation takes into account planned down time, which can be configured through Precise AdminPoint. For more information, see the Precise Administration Guide.
When Report Manager generates an Availability report, it checks if an instance availability falls below its availability threshold, unless there is no information (regarding availability) for the Tier. For example, a newly installed Tier may not have data currently available regarding availability; in this case a bar labeled Unknown appears on the graph. If an instance availability falls below its availability threshold, Report Manager sends an alert to Alerts. Likewise, when working in Alerts, you can drill down to the relevant Availability report from the Alerts user interface. For more information, see the Alerts User's Guide.
The Instance-level Availability report structure consists of the following sections:
The opening page of the Instance-level Availability report is similar to all the pre-defined reports except that the summary section provides information related to the specific report as follows:
The Tier Availability Table displays the availability details of each instance of the Tier. These details include the Average and Minimal Availability Percentage, and the Availability Threshold. The Availability Threshold can be configured through Precise AdminPoint. If the Instance Availability is below the threshold, Report Manager indicates its data in red. If there is no data currently available regarding availability, Report Manager indicates no data as Unknown and in blue.
By default, Report Manager generates Overtime graphs only for instances whose availability is below their threshold. Therefore, only for these instances, the names in the Instance column of the table are links, while the others are not links. You can change this default setting so that all the names will be links. See Setting Availability report properties - filters tab.
Report Manager generates, by default, Overtime graphs for each instance that its availability is below the threshold. The Availability Overtime graphs include the following:
To generate Overtime graphs of instances with availability above the threshold, modify the report properties and rerun it. See Setting Availability report properties - filters tab.
The Availability Overtime graphs contain a launching link to the related Precise or Insight product. You can click the launching link for further investigation in context of the displayed instance.
The Entity-level Availability report structure consists of the following sections:
The following information is displayed for each instance:
The opening page of the Entity-level Availability report is similar to all the pre-defined reports except that the summary section provides information related to the specific report as follows:
This Summary Table compares all the instances of the Tier by the availability of their entities. The Summary table contains a row for each reported instance that displays:
The Entities Availability Table displays the availability details of each entity in the current instance. These details include the Average and Minimal Availability Percentage, and the Availability Threshold. The Availability Threshold can be configured through Precise AdminPoint. If the entity availability is below the threshold, Report Manager indicates its data in red.
By default, Report Manager generates Overtime graphs only for entities whose availability is below their threshold. Therefore, only for these entities, the names in the System column of the table are links, while the others are not links. You can change this default setting so that all the names will be links. See Setting Availability report properties - filters tab.
Report Manager generates, by default, Overtime graphs for each entity that its availability is below the threshold. The Availability Overtime graphs include the following:
To generate Overtime graphs of entities with availability above the threshold, modify the report properties and rerun it. See Setting Availability report properties - filters tab.
The Availability Overtime graphs contain a launching link to the related Precise or Insight product. You can click the launching link for further investigation in context of the displayed entity.
The Availability Overview report structure consists of the following sections:
The opening page of the Availability Overview report is similar to all the pre-defined reports except that the summary section provides information related to the specific report as follows:
The Availability Overview Table lists for each instance of the Tier the availability information for each level, that is, instance-level and any entity for which availability information is being collected.
The table contains a row for each reported instance that displays the Instance Availability Percentage, the Total Amount of Entities for each entity type and their Average Availability Percentage.
The Cross-Tiers Availability report structure consists of the following sections:
The opening page of the Cross-Tiers Availability report is similar to all the pre-defined reports except that the summary section provides information related to the specific report as follows:
The Application Availability table displays the availability details of each Tier in the application. These details include the Average and Minimal Availability Percentage, and the Availability Threshold. The Availability Threshold can be configured through Precise AdminPoint. If the instance availability is below the threshold, Report Manager indicates its data in red.
By default, Report Manager only generates Overtime graphs for Tiers whose availability is below their threshold. Therefore, only for these Tiers, the names in the Tier column of the table are links, while the others are not links. You can change this default setting so that all the names will be links. See Setting Availability report properties - filters tab.
Report Manager generates, by default, Overtime graphs for each Tier of which its availability is below the threshold. The Availability Overtime graphs include the following:
To generate Overtime graphs of Tiers with availability above the threshold, modify the report properties and rerun it. See Setting Availability report properties - filters tab.
The Properties dialog box for the Availability reports contains two tabs in which you can set the properties:
In addition to these tabs, there is a Description tab which displays a textual description of the report structure and contents.
The Time Frame tab contains the following properties:
To set Availability report properties - time frame tab
The Filters tab contains the following properties:
To set Availability report properties - filters tab
Load Balancing reports assist you to maintain the application balanced, by providing information about servers that are loaded more or less than others.
Report Manager provides two types of Load Balancing reports:
Report Manager compares the servers' load using the operating system counters. Therefore, these reports are only available when Insight's OS Tier is installed.
For more information, see the Precise Installation Guide. The operating system counters include:
Report Manager compares the servers also by the Tier's Total Time, Volume, and Average Time. To overcome the differences among the servers' power (such as, CPU and memory), the different servers are assigned with weights. By default, a UNIX server is weighted 7 and a PC is weighted 4. The Total and Average Times are multiplied by the weight. The weights of the servers are stored in the Performance Management Database and can be updated using appropriate SQL UPDATE statements.
In the report properties, you can set the deviation percentage from the average, by which Report Manager determines if the server is loaded. If the server is overloaded or below the average load, Report Manager sends an event to Alerts.
Report Manager generates the Tier Load Balancing report for all the servers that run instances of the specified Tier (Report Manager does not generate the Tier Load Balancing report for Tiers that contain a single server).
The Cross-Tiers Balancing report structure consists of the following sections:
The opening page of the Cross-Tiers Load Balancing reports is similar to all the pre-defined reports except that the summary section provides information related to the specific report as follows:
The Cross-Tiers Balancing Heat Matrix summarizes the load of each server in the application. Each row in the Balancing Heat Matrix represents a different server, and each column represents one of the balanced OS counters: CPU Usage, CPU Load, and Paging.
The color of the cell indicates the balancing state of the selected OS counter for the current server. Red indicates an overloaded server and orange indicates that the server load is under average.
The Heat Matrix also introduces technologies indicating where instances are installed on each server.
The Tier Load Balancing report structure consists of the following sections:
The opening page of the Tier Load Balancing reports is similar to all the pre-defined reports except that the summary section provides information related to the specific report as follows:
Report Manager generates an OS Summary graph for each balanced OS counter, such as CPU Usage and CPU Load and Paging. This graph displays the Counter Summarized Value versus the Average Load, for each reported machine.
Report Manager generates an OS Overtime graph for each balanced OS counter, such as CPU Usage, CPU Load and Paging. This graph displays an Overtime Behavior graph of the Top n and Bottom m Servers compared to the Counter Average Value.
This graph displays a Summary of the Overtime Behavior of the reported Tier. It displays the Actual Values of the counters for the Top n and Bottom m Servers.
Report Manager generates a Tier Overtime graph for each of the following counters:
This graph displays a Summary of the Counter Values for each installed Tier on the Top n and Bottom m Servers. Report Manager generates a Tier Consumption Summary graph for each of the following counters:
The Properties dialog box of the Load Balancing report contains three tabs in which you can set the properties:
In addition to these three tabs, there is a Description tab which displays a textual description of the report structure and contents.
The General tab contains the following properties:
To set Load Balancing report properties - general tab
The Time Frame tab contains the following properties:
To set Load Balancing report properties - time frame tab
The Filters tab contains the following properties:
To set Load Balancing report properties - filters tab
The Capacity Planning report provides a forecast about future consumption of the current instances. This information is essential for planning your application evolution. For example, you can plan to acquire new hardware or to restrain the consumption (If you choose to restrain the consumption, you can use the Profile reports set to detect the top consumers of the specific resource).
Capacity Planning reports take into consideration only the current active systems, and do not assume any new programs and enhancements, which may be applied in the future.
When Report Manager generates a Capacity Planning report, it checks if the expected increase in a forecasted counter exceeds the baseline by more than the increase threshold. In this case, it sends an alert to Alerts. Likewise, when working in Alerts, you can drill down to the relevant Capacity Planning report from the Alerts user interface. For more information, see the Precise Alerts User Guide.
A Capacity Planning report structure consists of the following sections:
The opening page of the Tier Capacity Planning reports is similar to all the pre-defined reports except that the summary section provides information related to the specific report as follows:
The Heat Matrix page indicates, in a tabular format, the most significant consumption increase of the forecasted counters. Each row in the Heat Matrix represents a different instance. Each column represents a different forecasted counter. The cell color indicates the increase level of the counter related to its increase thresholds. You can set the increase thresholds through the Capacity planning report - general tab of the report Properties dialog box. The instance name is a link to the instance’s Overtime Behavior graphs.
Report Manager generates - for each instance - a Behavior and Forecast Overtime graph for each predicted counter. Each Overtime graph presents the past behavior, baseline, and forecast of the counter.
The Behavior and Forecast Overtime graphs page contain a launching link to the related Precise or Insight product. You can click the launching link for further investigation in context of the displayed instance.
The Properties dialog box of the Capacity Planning report contains three tabs in which you can set the properties:
In addition to these three tabs, there is a Description tab which displays a textual description of the report structure and contents.
The General tab contains the following properties:
To set Capacity Planning report properties - general tab
The Time Frame tab contains the following properties:
To set Capacity Planning report properties - time frame tab
The Filters tab contains the following property:
To set Capacity Planning report properties - filters tab
|