Skip Headers
Oracle® Real User Experience Insight User's Guide
Release 11.1 for Linux x86-64

Part Number E22309-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

4 Working With the Diagnostics Facility

This chapter explains the use of the diagnostics facility. This provides a powerful means for Application Managers and IT technical staff to perform root-cause analysis of operational problems. It supports session performance breakdown, including the impact of failing pages and hits on sessions, the full content of each failed page, and the relationship between objects, page views, and sessions. Diagnostics for Web services is also available to investigate failed function calls.

4.1 Introduction

When problems are identified, the diagnostics facility offers a means to drill-down into RUEI's rich data structure and both assess the impact of the problem on your Web site's visitors and Web services, and obtain direct insight into possible causes.


In order for session replay data to be available, session recording must be enabled. This is described in Section 13.5, "Masking User Information".

The Error Recording Facility

In addition to the information described above, RUEI also offers the opportunity to track exactly what error messages visitors to the monitored Web site receive, and when. With this ability to recreate application failures, you can accurately and immediately eliminate annoying and problematic parts of your Web pages.

Understanding Session Reporting

Information about user sessions is reported within the diagnostics facility as user records. It is important to understand that information is reported using a resolution of five minutes. The properties associated with it, such as IP address and user ID, are effectively snapshots taken at the end of the 5-minute period. Note that while the value of these properties can potentially change during the 5-minute period, it is their values at the end of the period that are reported.

Using the Diagnostics Facility

To locate the diagnostics information you require, do the following:

  1. Select Browse data, and select the group from which you want to start. Diagnostics information is available from within the All sessions group, the Service test group, the Failed URLs, pages, and functions groups, as well as the accelerator-specific groups (such as Oracle E-Business Suite and Siebel). Click the required diagnostics option. Note the name of the option reflects the selected group. For example, Session diagnostics, Page diagnostics or URL diagnostics. A diagnostics panel similar to the one shown in Figure 4-1 appears.

    Figure 4-1 Diagnostics Panel

    Description of Figure 4-1 follows
    Description of "Figure 4-1 Diagnostics Panel"

  2. Use the Calendar controls (described in Section 2.5, "Using the Calendar") to select the required period. The selected viewing range must be a single day (or less). If you attempt to search outside this limit, an error is reported. The availability of replay content is determined by the associated Collector retention policies (described in Section 13.7, "Defining Collector Data Retention Policies").

  3. Use the search facility to locate the required user record(s). The specific criteria available depends on the selected group. The available search criteria are shown in Table 4-1. Note that only the first 100 items are listed within each criteria menu. Therefore, if the required item is not listed, you can use the Search icon to the right of the appropriate criteria field to locate and select it. The Exit diagnostics icon returns you to your position within the Data Browser immediately before you entered the diagnostics facility.

    Table 4-1 Diagnostics Search Criteria

    Data Browser Group All sessions Service tests Failed pages Failed URLs Slow URLs E-Business Suite Siebel PeopleSoft JD Edwards

    Application name


    User ID



    Client IP address




    Service name



    Beacon name



    Object URL



    Object delivery



    Object URL



    Client network


    EBS responsibility



    Siebel method



    PeopleSoft node name



    JD Edwards form


    Optionally, you can specify additional search criteria using the Add more filters facility. As with the primary search criteria, the additional search filter options depends on the selected group. Be aware that all criteria specified for the search must be meet for matched user records to be reported, and that exact searching is used. All strings are regarded as literals, and the use of wildcards is not supported.

    For a number of diagnostics groups, you can also specify the order in which matched user records are reported through the Search result order facility. When ready, click Search. The results of the search are shown in the main part of the window. An example is shown in Figure 4-2.

    Figure 4-2 Session Diagnostics Window

    Description of Figure 4-2 follows
    Description of "Figure 4-2 Session Diagnostics Window"

  4. Use the controls in the toolbar at the top of the window to scroll between result pages. A maximum of 100 user records are listed per page. You can select a specific user record from the displayed list by clicking it.

    Optionally, use the Order menu to specify the order in which matched user records are listed. In addition, you can use the Dimension level and Value menus to apply additional filters to the displayed list. When ready, click Add. The options available within the Dimension level menu depends on the selected group.

    Note that you can select the Export session option from the user record context menu shown in Figure 4-2. The use of this facility is described in Section 4.4, "Exporting Full Session Information".

  5. After selecting a user record, the View part of the panel in the left-hand side of the window allows you to view information about the selected user record. Use the Pages, Object, and Info items under the Session part to view information concerning specific aspects of the selected user record. An example is shown in Figure 4-3.

    Figure 4-3 Example Diagnostics Panel

    Description of Figure 4-3 follows
    Description of "Figure 4-3 Example Diagnostics Panel"

    Session pages are grouped so that when expanded their associated objects can be viewed. The overview shows the pages (and their times) recorded within the selected user record. Icons indicate slow or failed objects, page loading satisfaction, whether the pages are key pages, and whether replay content for them is available. The use of the Replay viewer is described in Section 4.2, "Replaying User Sessions".

    Note you can use the Include/Exclude spurious objects icon within the toolbar to control whether hits not directly associated with a reported page are included in its displayed list of objects. This facility is particularly useful in the identification of problem objects that have an extremely long load time. Normally, these objects would not have associated pages and, therefore, would not be listed in the session page report.

    The Export session pages command button allows you to export a summary of the currently selected user record to Microsoft Excel. The use of this facility is explained in Section 4.3, "Exporting Session Pages to Microsoft Excel".

  6. You can click the Pages or Objects option under the View part of the panel to review a summary of pages viewed by the visitor or the objects within them. An example is shown in Figure 4-4.

    Figure 4-4 Example Page Properties Dialog

    Description of Figure 4-4 follows
    Description of "Figure 4-4 Example Page Properties Dialog"

    Within the displayed page history, the full page content, as well as the underlying HTML code of the messages received by the server and client are also available. Be aware that the reported contents are subject to the currently defined masking options for HTTP protocol items. Detailed application and session-related information about the page or URL is available via the Info option. An example is shown is shown in Figure 4-5.

    Figure 4-5 Example Session Information

    Description of Figure 4-5 follows
    Description of "Figure 4-5 Example Session Information"

  7. When ready, you can click the Remove icon beside the selected user record. You are returned to the diagnostics window shown in Figure 4-2. From here, you can select and drill down into other user records.

Masking Sensitive Information Within the Diagnostics Facility

As mentioned earlier, the availability of information (such as header or URL information) within the diagnostics facility can be controlled through the appropriate HTTP protocol item masking facility. This is described in Section 13.7, "Defining Collector Data Retention Policies".

4.2 Replaying User Sessions

When available, you can click the Replay icon beside a viewed page to replay the complete user session. This provides the opportunity to review each page viewed by the visitor during the session, together with any reported error messages. An example is shown in Figure 4-6.

Figure 4-6 Example Session Replay

Description of Figure 4-6 follows
Description of "Figure 4-6 Example Session Replay "

The replay details are shown in a new window which is the same size as the main window. Note that if selected by clicking the Replay icon for a page within a selected user record, the displayed page history starts from the point of the selected page.

The controls below the page listing allow you to navigate through the page history. The Page information section indicates the currently highlighted page's loading satisfaction, whether it is key page, and whether it contains an error.

Reporting Page Events

If a viewed page contained HTTP form elements, these and the visitor replies are reported in the Page events panel. Unnamed elements are reported as "NO_NAME_number" (where number is incremented for each unnamed element). Hidden form elements are also reported. Be aware that the replies made by a visitor to form elements is derived from the request body of the next page in the session page view history. Therefore, if the visitor switched context to another page between the request and response pages, the user response cannot be extracted and reported.

The status bar at the bottom of Figure 4-6 provides information about the session user ID, each page's recorded timestamp, loading time, number of objects and (in the case of static pages) an indication that reported pages are retrieved from the live source (such as the application server).

Viewing Page Content

The HTTP content command button on the toolbar allows you to view the actual request and response content of the currently selected page. An example is shown in Figure 4-7.

Figure 4-7 Example Page Content

Description of Figure 4-7 follows
Description of "Figure 4-7 Example Page Content"

Note that external JavaScript files can also be viewed by clicking the link within the page content. The reported content of these files is retrieved from the live source (for example, an application server).

Viewing Static Page Content

If no Replay icon is available beside a page in the displayed viewing history, this indicates that the page's content is not available. This can be because the information is expired due to data storage constraints, or because the viewed page was a static page. In the case of the latter, you can still view the static page's content by highlighting the page immediately before or after the static page in the viewing history, and via this page, view the static page's content.

Be aware that the reported content for the objects on a static page is retrieved from the live source. Hence, if the live source is not available for any reason, the page's content may not be correctly reported. In addition, data masking and JavaScript execution rules are not applied to any page contents retrieved from the live source. The page contents are shown "as is". Note that if a static page was cached at the client, an earlier complete page fetch for any session is used for the preview. Therefore, depending upon the configuration of the monitored Web site, this may have been modified since the visitor actually viewed the page. For example, a page listing current stock market prices. When live source data is reported, this is indicated in the Replay status bar.

JavaScript Execution Within the Replay Viewer

Pages viewed by visitors can contain inline JavaScript code. The application definition facility allows you to specify how execution of this JavaScript code should be handled within the replay facility. This is fully described in Section 8.2.17, "Controlling JavaScript Replay Execution". In addition, be aware that suites (such as Siebel and PeopleSoft) have preconfigured JavaScript execution rules that optimize their reporting within the Replay viewer.

4.3 Exporting Session Pages to Microsoft Excel

You can export a summary of the pages within the currently selected session to Microsoft Excel. To do so, do the following:

  1. Select the required session using the procedure described earlier. Click the Export session pages command button. Depending on how your browser is configured, you are either prompted to specify the tool with which to open the file directly (by default, Microsoft Excel), or it is immediately saved to the defined default location.

  2. Within Microsoft Excel, you can view and edit the generated file. An example is shown in Figure 4-8.

    Figure 4-8 Example Microsoft Excel Session Pages Export

    Description of Figure 4-8 follows
    Description of "Figure 4-8 Example Microsoft Excel Session Pages Export"

The exported page view history and session summary can be used to compile sets of real-user sessions. For example, to be used as the basis for testing or performance analysis.

4.4 Exporting Full Session Information

In addition to viewing session information, you can also export complete session contents to external utilities for further analysis or integration with other data. For example, this offers the opportunity to use complete real-user sessions as the basis for test script generation. Test platforms, such as Oracle Application Testing Suite (ATS), can easily be configured to generate automated test scripts for an application's most commonly encountered usage scenarios.

In addition, this facility can also be used to support powerful root-cause analysis. Complete user session information can be provided to application or operations specialists to help identify unusual or difficult to isolate issues. Sensitive information within the exported data is masked according to the actions defined in the HTTP protocol item masking facility. This is described in Section 13.5, "Masking User Information".

To export session information, do the following:

  1. Locate the required session and select the Export session option from its context menu. This is shown in Figure 4-9.

    Figure 4-9 User Record Context Menu

    Description of Figure 4-9 follows
    Description of "Figure 4-9 User Record Context Menu"

    Alternatively, within the Replay facility, select the Session menu, and then select the Export session option. In either case, a dialog appears prompting you to confirm exportation of the selected session.

    It is important to understand that the exported data may contain sensitive information. It is recommended that you carefully review the session's contents to ensure that sensitive information has been correctly masked. To confirm export of the selected session, click Yes.

  2. Depending on how your browser is configured, you are either prompted to specify the location to which the zip file should be saved, or it is immediately saved to the defined default location.


In order for the session export files to be created correctly, you should ensure that:

In addition, it is recommended that you verify the exported content files (described in the following section) are present before attempting to import an exported RUEI session into an external utility.

Understanding the Structure of the Exported Data

The exported session zip file contains the following files:


The log files used as the basis for creating exported session files are also used internally by RUEI. The format and contents of these files is subject to change without notice.

4.5 Configuring Clickouts to External Tools

The URL diagnostics group (described in Section 3.2.4, "The URL Diagnostics Group"), the suite diagnostics groups (described in Section 3.2.5, "Suite Groups"), and Session diagnostics facility (described in Section 4.1, "Introduction") support clickout from selected functional URLs and certain dimensions to external diagnostics utilities. The currently supported external utilities are shown in Table 4-2.

Table 4-2 Supported Clickout Tools

Utility Description

AD4J 10gFoot 1 

Oracle Application Diagnostics for Java (AD4J) is part of the Oracle diagnostics pack for Oracle middleware, and provides low-overhead monitoring and diagnostics functionality to improve Java application availability and performance.

The use of this facility requires AD4J 10g R4 to be installed within your organization.

Business Transaction ManagementFoot 2 

Oracle Business Transaction Management (BTM) is a utility that brings real-time visibility to business transactions. It enables organizations to identify and resolve transaction errors, failures, and bottlenecks, or respond quickly to prevent an isolated problem from turning into a global outage.

CAMM 10gFootref 1

Oracle Composite Application Monitor and Modeler (CAMM) is a utility that allows you to monitor highly distributed Java EE and SOA applications running within your organization.

The use of this facility requires CAMM 10g R4 to be installed within your organization.

EBSFoot 3 

Refers users to the server or user reports facility on your EBS deployment.

EMGC 11Footref 1

Depending on your installed Oracle Enterprise Manager middleware and application management packs, the following facilities are available:

  • JVM diagnostics (previously available as AD4J).

  • Request monitoring (enhanced AD4J/CAMM support).

  • Application dependency (previously available as CAMM).

My Oracle SupportFoot 4 

Searches the Oracle Customer Services' Web site (My Oracle Support) for relevant information about specific reported errors. For example, ORA-12154 or SBL-UIF-00271.

Use of this facility requires a working My Oracle Support registration. Further information is available at the following location:

SiebelFoot 5 

Refers users to the server overview or user search facility on your Siebel deployment.

Footnote 1 The URL dimension within URL diagnostics and Session diagnostics groups.

Footnote 2 Pages and dynamic objects identified by BTM in the BTM service dimension within URL diagnostics and Session diagnostics groups.

Footnote 3 Applications names, page URLs, EBS suite names, and user IDs within the EBS and Session diagnostics groups. User IDs are directed to the user reports facility, while all other items are directed to the server reports facility.

Footnote 4 Content error dimensions. Note that clickout is only available for standard errors (such as ORA-06512), and not user-defined content errors (such as "Out of stock").

Footnote 5 Application names, page URLs, Siebel suite names, and user IDs within the Siebel and Session diagnostics group. User IDs are directed to the user search facility, while all other items are directed to the server overview facility.

Configuring Clickout Functionality

To configure access from within RUEI to these utilities, do the following:

  1. Click the Configuration tab, then General, then Advanced settings, and then Clickout settings. Note that this option is only available to Administrators. Click Add new item or an existing external utility definition. A dialog similar to the one shown in Figure 4-11 appears.

    Figure 4-11 Edit Clickout Setting

    Description of Figure 4-11 follows
    Description of "Figure 4-11 Edit Clickout Setting"

  2. Use the Clickout tool menu to select the external utility whose interface you want to configure. The supported utilities are shown in Table 4-2. Note that the other fields available within the dialog depend on the selected utility.

  3. Use the Host field to specify how the selected external utility should be reached. This should not include the protocol scheme (such as http://). For example,

  4. Use the Port field to specify the required port number. Only one port number can be specified. A wildcard character (*) cannot be specified.

  5. Use the Extensions entry field to specify the object file extensions for which clickout should be available. Use the Add button to specify additional extensions. You can also use the Also allow no extension check box to specify whether hits with no associated file extensions should have clickout availability.

  6. Click the Advanced tab, and use the Protocol field to specify whether HTTP or HTTPS is used for connection to the selected utility. By default, HTTP is used.

  7. Use the Regular expression and Replace fields to specify the parts of the URL passed to the external application that should be replaced. Further information on the use of regular expressions is available from Knowledge Vase articles within the My Oracle Support Web site. This is available at the following location:

    When ready, click Save. Any changes made to these settings are applied immediately.

Application and Suite Configuration

For each required application, specify the functional URLs that support clickout. This is described in Section 8.2.16, "Controlling Reporting Within the URL Diagnostics Group".

For Oracle E-Business Suite (EBS) and Siebel suites, the Enterprise name must be specified as part of a suite's configuration in order for clickout functionality to be available within dimensions. This is described in Section 10.1, "Working With Suites".

Access to Clickout Functionality

Clickout functionality for Data Browser items is available via the item's context menu. The exact options available to you depend on the Data Browser group, the selected dimension, and the defined clickout settings. An example is shown in Figure 4-12.

Figure 4-12 URL Diagnostics Group

Description of Figure 4-12 follows
Description of "Figure 4-12 URL Diagnostics Group"