Load vs Response Time Analysis Report
Administrators may often wish to know how healthy the business transactions were over a period of time and on which date/time the business transactions were slow and error-prone. They would also wish to analyze the business transaction load over a period of time. This analysis would help administrators in figuring out the root cause of why the transactions were slow and error-prone and when exactly the transactions were slow. Additionally, administrators may want to historically analyze which server was contributing more load in terms of business transaction. The Load vs Response Time Analysis report helps administrators in such analysis.
This report helps administrators generate a historical analysis of the transaction health and figure out how many transactions were healthy, slow, stalled and error-prone with respect to the response time. The exact day/date and time of when the transactions were slow, error-prone and stalled can be identified with ease using this report. The server that is contributing the most in terms of business transactions can be identified and the load of the server can be analyzed. This report also offers insights into the top business transactions over a period of time.
In order to generate the Load vs Response Time Analysis report, do the following:
- Follow the menu sequence: REPORTS BY FUNCTION -> Domain-specific Reports -> Web Application Monitoring -> Business Transaction Monitoring -> Load vs Response Time Analysis.
Using this report, you can analyze the performance of one/more managed components, or those that are part of a zone, service or segment. The options provided by the Analyze By list box are discussed hereunder:
- Component: Select this option to choose the component(s) from across all the managed components in the environment.
- Zone: To generate a report for one/more components that are included in a zone, pick the Zone option. A Zone drop-down list will then appear, from which you would have to select the zone to which the components of interest to you belong. A Sub zone flag also appears. Indicate whether the components present within the sub-zones of the chosen zone are also to be to be considered for report generation, by setting the Sub zone flag to Yes.
- Segment: If you want to generate a report for one/more chosen components that belong to a segment, select the Segment option from Analyze By list box, and then pick the Segment from the drop-down list that appears.
- Service: If you want to generate a report for one/more components involved in the delivery of a service, select the Service option from Analyze By, and then pick the required Service from the drop-down list that appears.
- Then, select a component type for which you wish to generate the report from the Component Type list.
- The Component list will now be populated with all the components that are managed in your environment for the chosen component type. If the Components list consists of too many components, then viewing all the components and selecting the ones you need for report generation could require endless scrolling. To avoid this, you can click the button next to the Components list. A COMPONENTS pop up window will then appear using which you can view almost all the components in a single interface and Select the ones to be included in this report.
- Select the business transaction for which the report is to be generated for a chosen time period from the URL list. By default, All option is chosen from this list.
Then, specify the Timeline for the graph. You can either provide a fixed time line such as 1 hour, 2 days, etc., or select the Any option from the list to provide a From and To date/time for report generation.
For every user registered with the eG Enterprise system, the administrator can indicate the maximum timeline for which that user can generate a report. Once the maximum timeline is set for a user, then, whenever that user logs into eG Reporter and attempts to generate a report, the Timeline list box in the report page will display options according to the maximum timeline setting of that user. For instance, if a user can generate a report for a maximum period of 3 days only, then 3 days will be the highest option displayed in the Timeline list - i.e., 3 days will be the last option in the fixed Timeline list. Similarly, if the user chooses the Any option from the Timeline list and proceeds to provide a start date and end date for report generation using the From and To specifications, eG Enterprise will first check if the user's Timeline specification conforms to his/her maximum timeline setting. If not, report generation will fail. For instance, for a user who is allowed to generate reports spanning over a maximum period of 3 days only, the difference between the From and To dates should never be over 3 days. If it is, then, upon clicking the Run Report button a message box will appear, prompting the user to change the From and To specification.
In addition to the settings discussed above, this report comes with a set of default specifications. These settings are hidden by default. If you do not want to disturb these default settings, then you can proceed to generate the report by clicking the Run Report button soon after you pick one/more components for report generation. However, if you want to view and then alter these settings (if required), click on the icon. The default settings will then appear in the MORE OPTIONS drop down window (See Figure 2). The steps below discuss each of these settings and how they can be customized.
If the timeline specified for the report needs to exclude the data collected during the Weekends, then set Exclude weekends to Yes. If not, select No.
By default, the weekend constitutes Saturday and Sunday. To override this default setting, do the following:
- Edit the eg_report.ini file in the <EG_INSTALL_DIR>\manager\config directory.
- In the [EXCLUDE_WEEKEND] section of the file, the Days parameter is set to Saturday,Sunday by default. You can modify this by setting the Days parameter to a comma-separated list of other days of the week - say Friday,Saturday.
- Save the file after making the required changes.
- By default, the check box in front of the Server Aggregate option is chosen indicating that the business transactions over a period of time will be consolidated for all the components chosen from the Component list in the generated report. However, if you uncheck this option, then, the generated report will show the business transactions for each individual component.
Specify the Time Interval for which this report is to be generated. By default, the Time Interval is 1 day. This implies that the URLs are consolidated together and the graph of this report is plotted for each day. If you choose 30 mins from the Time Interval list, then the graph will be plotted for every 30 minutes.
If you have chosen a Timeline of 1 week and above, it is not advisable to choose 30 mins and 1 hour options from the Time Interval list.
- By default, Transactions option is chosen from the Measures list indicating that the report will be generated based on the transactions performed on the server over a period of time. However, in environments where more transactions are performed per minute, administrators may want to analyze the load of the server by analyzing the transactions performed per minute. For this purpose, administrators can choose the Transactions/min option from the Measure list.
- By default, the check box in front of the Showing Entry Node Only option is checked indicating that the report is generated only for the first transaction performed by the user on the chosen component. However, if you wish to generate the report for all the business transactions, then, you may uncheck the check box.
Next, indicate the report Time period.
By default, the Time period is set to 24 hours. Accordingly, the From and To parameters in the [timeframe] section of the eg_report.ini file (in the <eg_install_dir>\manager\config directory) are set to 00:00 and 24:00 respectively. If need be, you can override this default setting by configuring a different timeframe against the From and/or To parameters.
In large environments, reports generated using months of data can take a long time to complete. Administrators now have the option of generating reports on-line or in the background. When a report is scheduled for background generation, administrators can proceed with their other monitoring, diagnosis, and reporting tasks, while the eG manager is processing the report. This saves the administrator valuable time. To schedule background processing of a report, you can either select the Background Save - PDF option from the Report Generation list. To process reports in the foreground, select the Foreground Generation - HTML option from this list.
- The Report Generation list will appear only if the EnableBackgroundReport flag in the [BACKGROUND_PROCESS] section of the eg_report.ini file (in the <EG_INSTALL_DIR>\manager\config directory) is set to Yes.
- The default selection in the Report Generation list will change according to the Timeline specified for the report. If the Timeline set is greater than or equal to the number of days specified against the MinDurationForReport parameter in the [BACKGROUND_PROCESS] section of the eg_report.ini file, then the default selection in the Report Generation list will be Background Save - PDF. On the other hand, if the Timeline set for the report is lesser than the value of the MinDurationForReport parameter, then the default selection in the Report Generation list will be Foreground. This is because, the MinDurationForReport setting governs when reports are to be processed in the background. By default, this parameter is set to 2 weeks - this indicates that by default, reports with a timeline of 2 weeks and above will be processed in the background.
- Finally, click the Run Report button to generate the report.
If the Report type is Foreground Generation - HTML, then Figure 3 will appear as soon as you click the Run Report button.
- From the Traffic section of Figure 3, you can figure out the total number of transactions performed for the chosen component. The Heat map chart in this section helps administrators in identifying the health of the transactions, in percentage. The percentage of slow and error-prone transactions can also be inferred from this chart.
- The average response time and the maximum response time (the Response Time section in Figure 3) of the business transactions help administrators with an overview of the time spent on a business transaction.
- The Errors section helps administrators identify the count of error-prone transactions.
- From the Traffic vs Response Time section in Figure 3, you can figure out the health of the URLs of the chosen components and the response time taken for the transactions to complete over a period of time. Hovering over each bar provides you with the exact number of transactions that were healthy, slow, error-prone and stalled. Clicking on the icon against each type of transaction will lead you to the Business Transaction Monitoring - Slice and Dice Analytics Report.
- The Traffic vs Response Time Detail section will list count of transactions initiated over a period of time on each server, provides insights into the maximum response time and minimum response time of the server for the transactions. The count of error prone transactions for each server is also captured and reported. Clicking on the date/time in the REQUEST TIME column will lead you to the Business Transaction Monitoring - Slice and Dice Analytics Report.
- The Top 10 Business Transactions Health Report section in Figure 3 lists the top business transactions performed on the server over a period of time. Using this section, administrators can figure out if the transaction was healthy, slow or error-prone. Clicking on a business transaction will lead you to the Business Transaction Monitoring - Slice and Dice Analytics Report.
- On the other hand, if the Background Save - PDF option is chosen from the Report Generation list, then clicking on the Run Report button will not generate the report and display it in this page for your benefit. Instead, a message indicating that the report is being processed in the background will appear. This will be accompanied by a link that will lead you to the page that lists all the reports that are being processed in the background, and their current status. If background report generation fails for a report, you can regenerate that report using this page, or can even delete that report if need be. On the other hand, if background processing successfully completes for your report, then, you can view a PDF of the report by clicking on the icon in that page.