Understanding the Failure Report

Note: The Failure Report is currently a beta feature.

 

This topic includes the following information:

 

About the Failure Report

The Failure Report aggregates and displays failure and error events occurring on Rapid Recovery Cores, protected machines, and repositories. Each of these reporting levels (Cores, machines, and repositories) is segregated in the Failure Report UI into separate tabs.

The report uses for its default data the set of Cores, machines and repositories accessible to the logged-in user's root organization and all sub-organizations. This is a configurable parameter.

The report consists of the following three pages.

Analysis

The Analysis page of the Failure Report is where you can run or schedule a report. For more information, see Creating a report schedule. This page also shows the report results.

The criteria available for narrowing the scope of the report are determined by which reporting level is selected. The options are as follows:

  • Cores. Time Period, Organizations, Cores, and Event Types (command, event, or task failures).
  • Protected Machines. Time Period, Organizations, Cores, Machines, and Event Types.
  • Repositories. Time Period, Organizations, Cores, Repositories, and Event Types.

Following is a brief description of each report input parameter:

  • Time Period. When running a report, from this drop-down list you can select a time period defining the start and end time for data to be displayed in the report.

    Note: For clear definitions of each time period option, see Working with time periods in the topic Working with QorePortal reports.

    Local times are converted to Coordinated Universal Time (UTC).

    Note: To understand the effect of UTC date conversion on the returned data set, see Understanding dates shown in QorePortal reports in the topic Working with QorePortal reports.


  • Organizations. Based on your root group, from this drop-down list you can select one or more organizations to define the scope of the report.

    Note: For more information, see Working with organizations in the topic Working with QorePortal reports.


  • Cores. From this drop-down list, you can choose the Rapid Recovery Cores you want to include in your report. The default is to include all of the Cores in the found set (defined by the other search criteria). This option lets you clear any Cores that you do not want to include in the report. This parameter is available for all reporting levels or the Failure Report.
  • Machines. From this drop-down list, you can choose the protected machines to include in your report. The default is to include all of the protected machines in the found set (defined by the other search criteria). This option lets you clear any machines that you do not want to include in the report. This parameter is available only for the Machines reporting level for the Failure Report.
  • Repositories. From this drop-down list, you can choose the repositories to include in your report. The default is to include all repositories for all Cores in the found set. This option lets you clear any repositories that you do not want to include in the report. This parameter is available only for the Repositories reporting level for the Failure Report.
  • Types. From this drop-down list, you can choose the event types to include in your report. The default is to include all types (Commands, Events, and Tasks).

    Note: Since this report requires manipulation of hundreds or thousands of event types, to improve performance, reduce the number of records required to generate the report by clearing the event type "Event."

The results of the report for the Cores reporting level appear as the following collection of and tables:

  • Summary is a single-row table summarizing the number of Core servers, protected machines, repositories, and failure events for the filtered set of parameters.
  • Failure Statistics by Cores is a table listing one row for each failure event, by Core, in the found set. For each data point in the table, you can mouse over the information to see the full content if necessary. Columns include:
    • Core Server. This data includes a hyperlink to the dashboard for the relevant Core, so you can drill down further.
    • Status. A short status message related to the failure event.
    • Summary. A summary of the event failure.
    • Description. A brief description of the event failure.
    • Type. This shows the event type for the failure event.
    • End Time. This shows the end time for the event, converted to UTC.

The results of the report for the Machines reporting level appear as the following collection of graphs and tables:

  • Summary is a single-row table summarizing the number of Core servers, protected machines, and failure events for the filtered set of parameters.
  • Failure Statistics by Machines is a table listing one row for each failure event, by machine, in the found set. For each data point in the table, you can mouse over the information to see the full content if necessary. Columns include:
    • Core Server. This data includes a hyperlink to the dashboard for the relevant Core, so you can drill down further.
    • Machine. This data includes a hyperlink to the dashboard for the relevant protected machine, so you can drill down further.
    • Status. A short status message related to the failure event.
    • Summary. A summary of the event failure.
    • Description. A brief description of the event failure.
    • Type. This shows the event type for the failure event.
    • End Time. This shows the end time for the event, converted to UTC.

The results of the report for the Repositories reporting level appear as the following collection of graphs and tables:

  • Summary is a single-row table summarizing the number of Core servers, number of repositories, and total failure events for the filtered set of parameters.
  • Failure Statistics by Repositories is a table listing one row for each failure event, by repository, in the found set. For each data point in the table, you can mouse over the information to see the full content if necessary. Columns include:
    • Core Server. This data includes a hyperlink to the dashboard for the relevant Core, so you can drill down further.
    • Repository. This data includes a hyperlink to the dashboard for the relevant repository, so you can drill down further.
    • Status. A short status message related to the failure event.
    • Summary. A summary of the event failure.
    • Description. A brief description of the event failure.
    • Type. This shows the event type for the failure event.
    • End Time. This shows the end time for the event, converted to UTC.

Saved reports

The Saved Reports page of the Failure Reports area is where you can view or delete any Failure Reports that you chose to save. The portal stores reports in order by creation date.

Schedules

The Schedules page stores the scheduled reports created by following the procedure in Creating a report schedule. Here, you can edit schedules and delete them.

About beta reports

Quest Software considers customer feedback when developing new features, and sometimes includes these features in beta form. Our intention is to make the feature available to our customers as early as practical, and to gauge whether our efforts meet demand. With that in mind, help us to help you.

Quest actively encourages your feedback. Please use our Ideation portal to provide us with your feedback about the usefulness of this report. Tell us what features you like, what improvements or additions you would like to see in the future, and what aspects of the report are not useful to you. For more information, see Using the Ideation portal.