Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloudor on-prem performance issues
Application Crashes / Hangs Report
Event logs on Windows servers capture critical error conditions such as service crashes and application crashes on the servers, application and service hangs, and service errors. Since the crash/slowness experienced by any mission-critical program/service on a Windows server may affect the uptime of the dependent business services, administrators should be able to historically analyze these serious problem conditions, isolate the applications that crash repeatedly and investigate the pattern of problem occurrence. The Application Crashes / Hangs report helps administrators in this regard!
To generate this report, do the following:
Follow the menu sequence: REPORTS BY FUNCTION -> Analytical Reports - > Event Log Reports -> Application Crashes / Hangs. Figure 3 will then appear.
Using this report, you can analyze the crashes/hangs on the applications installed on 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:
Specify a Timeline for the report.
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 a Component Type. However, if you want to view and then alter these settings (if required), click on the button. The default settings will then appear in the MORE OPTIONS drop down window (see Figure 4). 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.
The Weekend settings for a Consolidated Zone report will apply to this report too.
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 or the Background Save - CSV option from the Report Generation list. In this case, a Report Name text box will appear, where you would have to provide the name with which the report is to be saved in the background. To process reports in the foreground, select the Foreground Generation - HTML option from this list.
If the Report type is Foreground Generation - HTML, then Figure 5 will appear as soon as you click the Run Report button.
The generated report (see Figure 5) contains the following sections:
The Details of Applications section will reveal the applications that encountered failures along with the count of crashes and hangs noticed. Drilling down each application will reveal Figure 6.
Using Figure 6, administrators can figure out the components on which the application failed, when exactly the failure occurred, what was the problem condition ( crash or hang) and the location at which the application was installed.