Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Run debug LEM reports

Run debug LEM reports

Table of contents
Created by Ezgi Muderrisoglu, last modified by Ezgi Muderrisoglu on Jun 30, 2016

Views: 937 Votes: 2 Revisions: 5



This article describes how to run reports for debug when raising a support case.


  • LEM 6.2
  • Reports Console & crystal runtime has been installed


If a technical representative has requested for debug reports, most likely they will be the following:

  • Database Maintenance Report
  • Agent Maintenance Report - 24 hours
  • Event Summary Graphs: 1 month
  • Inferred Alerts by Inference Report - 24 hours
  • Tool Maintenance by Alias Reports - 24 hours (This report can be large if there is a lot of unmatched data)


Requirement: User must already have the LEM reports console installed. If not, then install the reports console first, after this, follow the steps below for the reports mentioned above.


In this example, we demonstrate where to find and run the report for the Agent Maintenance Report.

The other reports on the list above fall under the same category, so they will be in the same list of reports. They all belong to the Category: Standard reports.


  1. Open the reports console.
  2. Make sure that the Category: Standard Reports has been chosen.
  3. User will then find a list of report titles of the out of the box standard reports. From this list, locate the reports that the Technical Representative has requested for. In this example, we have selected the Agent Maintenance Report.


  1. Once the report is chosen. Click on the Run button to run the report. 


  1. User will have the option to select the timeframe that the report should run for by changing the Start Date/Time and the End Date/Time. [Example: If user is looking for a report to give data on a months time period, then make sure a month time frame is chosen from Start date/time, to the End date/time. ]
    1. Alternatively for the End Date/Time a user can click on the Now button, to have the current date and time selected (also can be done for the Start date/time).


  1. After clicking the OK button, allow for some time for the report console to gather the requested information. Once it is collected, user will then see the desired report.
    1. IMPORTANT: Depending on the type of standard report chosen, different reports will have different results. There are some with just graphs, and others with just text based results. With the standard reports console, a user can not change the style of a standard report.
  2. Once the report is run, a user can select the Export button, and export the report.
    1. IMPORTANT: Pay close attention to the format of the report that the user is exporting. If a Technical Representative is looking for .RPT format, then this is the format that must be chosen when attempting to export. By default in most cases the reports are exported as a PDF. A user will have a chance to change the format after clicking on the Export button (in the View tab). Because of this, be ready to change to format of the export before clicking the final OK button to export the report.


Last modified