| Oracle® Real User Experience Insight User's Guide Release 5.1 for Linux x86-64 Part Number E15344-01 |
|
|
View PDF |
| Oracle® Real User Experience Insight User's Guide Release 5.1 for Linux x86-64 Part Number E15344-01 |
|
|
View PDF |
This chapter explains the use of the Data browser. This is at the heart of RUEI, and provides direct access to the information gathered during monitoring. Through it, you can drill down, search, and filter information in an intuitive and user-friendly interface.
The information shown in each report is derived from a multidimensional data structure that contains all the information captured during monitoring. Through this structure, you can explore Web data by simply clicking down through increasing levels of detail, and view by different dimensions (such as period, referrer, visitor type, and so on). This data structure can be viewed through the Data browser.
You can use the Data browser to understand the context of the data shown in a report, and to drill down, rank, sort, and filter information to gain insight into causes, effects, and trends. To open the Data browser from within a report, select Browse from the report menu. To open the Data browser from your home page (Figure 1-2), click Browse data. A window similar to one shown in Figure 3-1 appears:
The toolbar icons at the top of the Data browser screen are shown in Figure 3-2, and are described in Table 3-1:
| Icon | Description |
|---|---|
 Description of the illustration barcharticon.gif |
Graph. Displays the standard graphic visualization (pie chart, line chart, or bar chart) for the data. The graphic form depends on the underlying data. |
 Description of the illustration barrcharthorizicon.gif  Description of the illustration piecharticon.gif |
Additional visualizations. In addition to the standard graphical visualization, depending on the underlying data, additional visualizations may be available, and can be selected by clicking the appropriate icon. You can also use the Type option from the Graph menu to select a visualization. |
 Description of the illustration valuelisticon.gif |
Values. Shows the underlying data values for the data in the browser. See Section 3.3, "Working With Value Lists" for more information about working with value lists. |
 Description of the illustration rightgreenarrow.gif  Description of the illustration leftgreenarrow.gif |
Previous and Next page. Use these controls to move between pages in the displayed data set. |
 Description of the illustration informscreenicon.gif |
Glossary. Provides a brief explanation of the metrics currently shown within the browser. This includes both the dimensions shown in the graph or values table, and any filters that have been applied to it. The use of filters is explained in Section 3.6, "Working With Filters". |
 Description of the illustration searchicon.gif |
Search. Allows you to search for strings within in the current data set. The use of the search facility is described in Section 3.4, "Searching in the Data Browser". |
 Description of the illustration zoomin.gif  Description of the illustration zoomout.gif |
Zoom in and Zoom out. Allows you to change the level of displayed detail. When zooming in and out, you change the dimension of the viewed data. The new dimension depends on the currently selected dimension. For example, if you are viewing yearly data, zooming in will change the view to a monthly one. If you are viewing client location by country, zooming in will change the displayed dimension to providers within the client location country. To quickly return to the original dimension, select Reset view from the View menu. |
 Description of the illustration openasreporticon.gif |
Open as report. Opens a new window with the currently shown data in report print layout mode. The creation and customization of reports is fully described in Chapter 2, "Working With Reports." |
 Description of the illustration exporticon.gif |
Open as export. Opens a new window in which you can further customize the currently shown data prior to exporting it to a wide variety of applications (such as Microsoft Excel). This facility is fully described in Section 3.7, "Exporting Data". |
The information available within the Data browser is divided across groups. At the highest level, there are two types of groups: application-related groups and services-related groups. Each group provides a number of perspectives or views on the collected data. These views can be selected from the View selection panel, located on the left-hand side of the Data browser window (Figure 3-1).
Each main group within the View selection panel relates to a broad category of information. There are groups available about the pages visited on the monitored Web environment, visitor sessions, transactions, failed URLs and pages, and key pages.
Within each of these groups, sub-groups offer information about a specific aspect of the selected category. More specifically, they offer information across specific dimensions. These dimensions are indicated in the name of sub-group. For example, within the all sessions group, views are available across the dimensions domain, period, user ID, and client browser, language, location, and operating system. This is shown in Figure 3-3:
Figure 3-3 Data Structure Selection Panel
Individual views are grouped according to a standard classification (failure, performance, overall, and size) that reflects the type of information they provide. Within these, you can select the active dimension you want to use to explore the underlying data.
In addition to the standard dimensions discussed in this section, it is also possible to extend the information available within the Data browser through the use of custom dimensions. These are fully described in Section 3.8, "Defining Custom Dimensions".
The Session diagnostics facility is very described in Section 3.9, "Working With the Session Diagnostics Facility".
Within RUEI, two types of information available:
Real-time data: this has a delay of five minutes associated with it, and is based on the number of currently open sessions. This data is reported in dashboards and five of the Data browser views; the all pages, all services, failed functions, failed URLs, and slow URLs views.
Session-based data: this has a delay associated with it, and is derived from finished (client) sessions. The delay is the session idle time, described in Section 7.4.4, "Controlling Session Reporting". By default, it is 15 minutes. This data is reported in the Data browser views; all sessions, all transactions, failed pages, and key pages.
Why Are There Sometimes Differences in the Reported Data?
It is possible that small differences arise between the two different forms of reported data. For example, the number of reported visitors in the all pages view for a day may be slightly different to that reported in the sessions view. To understand why these differences can arise, it is necessary to understand how session-based data is processed.
Within the all sessions view, the client session information is reported as when the client session started. For all other views, the page view information is reported as when the page view started. Therefore, in the case of client sessions that started before, and went on after 12 PM, there will be differences in their associated reported dimensions.
Note:
Due to differences in the processing of real-time and session-based data, session-based views many indicate very slightly more (approximately 0.03%) page views than reported in real-time data for the same period.Timeliness Versus Accuracy
Session-based data provides the most accurate information about your monitored environment. However, if you feel that more immediate data is required, you could consider using one of the real-time data views in the Data browser. For example, using the all pages view instead of the all sessions view. However, while this has the advantage that the associated delay is only 5 minutes, client-specific information (particularly User-ID) is not available.
How Are Sessions Reported?
By default, session information is written to the All sessions group when:
The visitor has been inactive for more than 15 minutes.
The visitor session has lasted more than 60 minutes.
Both of these events are configurable, and are fully described in Section 7.4.4, "Controlling Session Reporting". The implications of these events are discussed below.
If, for example, a visitor session starts at 8:30 AM and ends at 5:30 PM, it will be considered closed every hour, and reported in the All sessions group every hour. However, within the session diagnostics facility, it is reported as a session from 8:30 AM to 5:30 PM.
Similarly, if a visitor has a session in the morning from 9:00 AM to 9:45 AM, and an afternoon session from 2:00 PM to 3:15 PM, three reported sessions appear in the All sessions group. In the session diagnostics facility, these two sessions appear as one user record from 9:00 AM to 3:15 PM.
The Problem analysis category of views (shown in Table 1-3) provides, for applications, in-depth information about failing or problematic page views and hits. It contains the following views:
Failed URLs
Reports on the objects (hits) within failed pages. For example, those pages that contain broken images and unavailable downloads. Note that it logs a maximum of 5000 objects per 5-minute period. All technical errors (described in Appendix E, "Explanation of Failure Codes") for that object are reported. Because this view is does not use application information, it can still report possible reasons for failed pages when no applications have been configured.
Failed pages
Reports on the server, network, Web site, and content errors experienced with pages inside applications.
Slow URLs
Reports on the slowest 5000 objects per 5-minute period detected by the system, based on the object's end-to-end time. Note that objects must have an end-to-end time of at least five seconds to be reported in this view. Applications do need to be configured for this view.
For services, it contains the following view:
Failed functions
Reports on the server, network, Web site, and content errors experienced with function calls.
Note:
The period for which information about failed URLs, pages, and service calls is available is determined by the Reporter system's data retention policies. These are fully described in Section 9.6.1, "Defining Reporter Retention Policies".The page delivery dimension is available within the Failed pages, All pages, Key pages views, and reports which errors have been detected on a monitored Web site. All errors reported in the page delivery dimension are also available through the Session diagnostics replay facility (see Section 3.9, "Working With the Session Diagnostics Facility").
Note if a page or object experienced several types of errors (for example, both a network and a Web service error), the page or object error is not recorded multiple times. Instead, it is reported according to the following order: Web site, server, network, and content. For example, an object that experienced both a Web site and a network error, is recorded as a Web site error rather than a network error.
The errors reported in this dimension are also available as the basis for KPIs as metrics expressed both as counters and percentages. This is shown in Figure 3-4.
When working with value lists, you can add additional columns to the displayed list. Select Show percentage or Show growth from the Values menu to add indicator columns to the displayed data. Note that availability of these options depends on the currently viewed list, and the columns are also carried forward when you view the list as a report (select Open as report from the View menu).
You can also change the sort order by selecting a column header at the top of the Values list. The view changes to reflect the selected column sorted in ascending order. Click it again, and the sort order becomes descending. The order symbol within a column heading indicates the current order. An example is shown in Figure 3-5:
Within value lists, you can also right click items to open the menu shown in Figure 3-6:
You can select:
Select value: adds the selected value as an inclusive filter to the Filters panel. That is, only values that match the selected value are displayed in the browser.
Exclude value: adds the selected value as an exclusive filter to the filters panel. That is, only values not matching the selected value are displayed in the browser.
You can use the Search facility to locate the incidence of strings in the currently displayed data set. This is shown in Figure 3-7:
The search facility will try to match any search pattern you specify either as a full match or as a substring. Hence, the search pattern "fire" will match the occurrences of "firefox", "x-fire", and "sefirewall", as well as, of course, all occurrences "fire". As mentioned earlier, the search is restricted to the currently displayed data. To extend the search further, you will need to modify the current view, or remove applied filters, and repeat the search. If the search did not find any matches, a pop-up dialog informs you that "No results were found".
Note:
The search facility does not support the use of wildcard characters (such as *). All characters are treated as literals. The results list is a values list and has the same functionality (see Section 3.3, "Working With Value Lists").To sort data in a graphic visualization, select the corresponding dimension from the legend beneath the graph. This is shown in Figure 3-8:
For information on sorting within a value list, see Section 3.3.1, "Changing the Sort Order".
In addition, you can use the Sorting option within the Data menu to undo any specified sorting specifications (Remove sorting), or swap the current sorting specification (Invert sorting).
You can use the Filter panel at the top of the browser window to tighten the profile of the information you want to view. An example is shown in Figure 3-9:
The first item shown in the filter panel is always the date or period for which information is required. In the example shown in Figure 3-9, this the year period 2007. This can be thought of as the highest-level filter, and can be changed through the calendar (explained in Section 2.4, "Using the Calendar").
After that, additional filters can be set. There are two kinds of filters: inclusive and exclusive. Inclusion filters specify that only data items that match the data value in the filter should be shown. Exclusive filters specify that only data items that do not match the data value in the filter should be shown.
For example, the filter profile in Figure 3-9 specifies that only information should be displayed for the year 2007 in which the client location was Liechtenstein, and the client browser was not Firefox.
You can define any data item within the browser window as a filter by right clicking it to open the menu shown in Figure 3-10. After you have defined a filter, you are free to modify it by clicking it and using the pop-menu shown in Figure 3-10:
The following options are available:
Invert: changes an inclusive filter into an exclusive filter, and vice versa.
Mark as report filter: the use of this option is described in Section 3.6, "Working With Filters".
Remove: deletes the selected filter.
Note:
Filters are applied in the order in which you define them. Once defined, it is not possible to change the order in which they appear in the filter panel. To re-order them, you must remove and redefine them in the required order.Within value lists, you can select multiple values by clicking the Multiple section command button, and then clicking each required value outside of the its associated link. The selected item(s) are then highlighted. An example is shown in Figure 3-13.
After selecting the required values, you can use the toolbar at the bottom of the screen to specify whether the values should be inclusive or exclusive filters. You can also use the toolbar to invert all currently defined filters, or to remove them.
Report filters can be used with reports that you create from the Data browser. When you specify a report filter for information you include in a report, the user opening the report can use the defined filter when viewing the report's contents.
For example, if you are viewing client location information (via the all sessions groups, and the client-location sub-group), you could create a report that allowed its users to select on client location. To define the filter, do the following:
Select a value from the displayed list of locations, and define it as a filter.
When displayed in the filter panel, right click it, and select Mark as report filter from the menu. An example is shown in Figure 3-12:
Note:
Only one report filter can be defined for each dimension. However, it is possible to define multiple report filters across different dimensions. Care should be taken when designing reports with multiple filters because it can make the report difficult to view.Select Open as report from the View menu, and finalize the structure of the required report. Notice that the selected filter is now shown in within the report. An example is shown in Figure 3-13:
Highlight the filter by placing the mouse pointer over it, and select Edit filter type from the menu. The Edit filter type(s) dialog shown in Figure 3-14 appears:
Use the check box(s) shown in the Edit filter type(s) dialog to control which filters can be selected by a user when the report is run. There will be a check box for each defined report filter. When ready, click Apply.
Save the report, as described in Section 2.9, "Creating New Reports".
Running the Report
When the report is run, and a report filter has been enabled, the value selected as the report filter becomes the default selection in a list of dimension values. An example is shown in Figure 3-15:
You can export the data currently shown in the Data browser to a wide variety of applications, such as spreadsheets. To start working with export data, open the Export window by clicking the Open as export icon, or selecting Open as export from the View menu. A new window with the current data is opened. An example is shown in Figure 3-16:
The Export window (Figure 3-16) shows the raw data that is available for export. However, you can customize how the data should be exported. To do so, right click within the export window, and select Edit. The Customize export dialog shown in Figure 3-17 appears:
This dialog allows you to modify the order of data columns, the order in which values appear in those columns, and specify additional columns that will appear in the Microsoft Excel export.
Within the Data columns and Value columns fields, you can use the lists to add additional primary (index) columns, and the data columns that should appear within them. The exact selection of data and value columns that are available within each list depends on the view group with which you are working. For example, if you are viewing data from the All clients group, the selection of Web site/page data columns is limited to domain and Web site. However, if you are working in All pages group, additional data columns are available for such things as page-content and page-transaction. For a complete description of the data and value columns that are available for export within each view group, see Appendix D, "Summary of Data Items."
The Percentage check box allows you to specify whether an additional column, showing the percentage make up from the reported values is added to the Microsoft Excel export.
The Growth check box allows you to specify whether an additional column, showing the actual increase in the reported metric, is added to the Microsoft Excel export.
You can use the Up, Down, and Remove icons next to a data column selection to control the sort order hierarchy, or to remove a data column as an index to the data. Similarly, you can use these controls within the value column field to rearrange the order in which they appear in the export.
You can save the export to a new or existing file, or append it to an existing export.
In addition to controlling how the exported data will appear, you can also specify the format in which the data will be exported. To do so, select the Download menu. The following export formats are available:
External tools working with the exported data should be aware that it is in Unicode (UTF-8) format.
Custom dimensions allow you to add your own user-defined dimensions to views in the Data browser. These new dimensions are then also available for use within KPIs, as well as reports and exports. For example, you might want to add a dimension "supplier" so that you could more easily track and analyze your organization's suppliers. Using this facility, you could determine which suppliers have the highest conversion rates associated with them within key business operations, or which suppliers attract the most pageviews on the organization's Web site.
Note:
Custom dimensions can be page, session, or function-based. Because KPIs are based on real-time data, session-based custom dimensions cannot be used as metrics within KPIs. However, page-based custom dimensions can be used as KPI filters. For more information, see Section 3.2.1, "Real-Time and Session-Based Data".Each custom dimension has a unique name, and is based on a source. This determines the group within which it appears, and can be page, session, or function-based. For example, page-based dimensions appear within the All pages and Failed pages groups, session-based dimensions appear in the All sessions and Failed pages groups, and function-based dimensions appear in the All functions and Failed functions groups.
Optionally, you can also define a set of translations for each unique source value reported for the dimension. For example, you could define the service-based custom dimension "server ID" with the associated translations shown in Table 3-2:
Table 3-2 Example Custom Dimension Translations
| Value | Translation |
|---|---|
|
178349 |
Business Partnerships |
|
561808 |
Newsletter and Events |
|
405969 |
Catalog |
|
969533 |
Payment Handling |
To define a custom dimension, do the following:
For function-based custom dimensions, select Configuration, then Services, and then Custom dimensions. For application-based custom dimensions, select Configuration, then Applications, and then Custom dimensions. A list of the currently defined custom dimensions appears. A maximum of five page or session-based custom dimensions can be defined. For function-based custom dimensions, the maximum is 10. Click the New dimension command button. The a dialog similar to the one shown in Figure 3-18 appears.
Specify a unique name for the new dimension. Note that in displays (such as within the Data Browser or a report) that feature the defined custom dimension, the dimension's name is appended with an asterisk (*).
Use the Based on menu to specify the entity type upon which the dimension should be based. For function-based dimensions, this is automatically selected as function, and cannot be modified. For application-based dimensions, you can selected this to be page, page (session aware), or session. The use of the page (session aware) option is explained in detail below. Note a maximum of five page or session-based custom dimensions, and a maximum of 10 function-based custom dimensions, can be defined.
Use the Number of levels menu to specify the level of dimension information that should be retained. By default, only one level of information is retained for the defined custom dimension. However, you can use this facility, together with the page (session aware) option to build a hierarchy of retained session information. For example, you might want to capture information about the user's location using the three levels of country, region, and city.
Use the Source type menu to specify the scope of the search for the dimension, and whether the search should use an XPath expression, a header, the cookie, a URL argument (request), or a custom tag. More information about using XPath queries is available in Appendix B, "Cookie Structures". More information about the use of custom tags is available in Appendix A, "Tagging Conventions". Note if the source is a URL argument, the raw (original) input is used. However, in the case of an HTTP header, only ASCII input is allowed. Non-ASCII characters are replaced by an underscore (_) character when reported. For more information encoding support, see Appendix B, "Cookie Structures".
When ready, click Save. An overview of the defined custom definition (similar to the one shown in Figure 3-19) appears.
Optionally, you can also define a set of translations for each unique source value reported for the dimension. To do so, click « Add new translations ». The dialog shown in Figure 3-20 appears.
Specify the required source value and its translation. When ready, click Save.
Note that if the list of imported translations is very large, you can use the controls at the bottom of Figure 3-19 to scroll through the displayed. In addition, you can use the search facility to locate a required translation. The search string can be specified in terms of either a source value or a translation. The use of wildcard characters (such as *) is not supported, and all characters are treated as literals.
Building Session Information Hierarchies
As explained earlier, by default only one level of information is retained for a custom dimension. However, you can use the page (session aware) option within the Based on menu to provide that a richer store of information is captured. For example, imagine that a Web site contains a sales catalog. An example of a user's browsing history is shown in Table 3-3.
Table 3-3 Example Session Information Retention
| Input | Dimension level | ||
|---|---|---|---|
|
1 |
2 |
3 |
|
|
a=men |
men |
men |
men |
|
(a=men,) b=coats |
men |
men » coats |
men » coats |
|
(a=men,) (b=coats,) c=winter |
men |
men » coats |
men » coats » winter |
|
(a=men,) b=hats |
men |
men » hats |
men » hats |
|
(a=men,) (b=hats,) c=trilby |
men |
men » hats |
men » hats » trilby |
|
a=children |
children |
children |
children |
This example features the use of three dimensions. The user starts browsing the men's section of the catalog. This represents the first dimension level. When the user selects the coats part of the catalog, this is captured in dimension 2, and the winter collection is captured in dimension 3. When the user changes to the men's hats section, the dimension 3 information is cleared, but dimension 1 and 2 information is retained. Similarly, when the user switches the children's section of the catalog, the dimension 1 information is updated, and the dimension 2 and 3 information is cleared. In this example, each of the dimensions are based on URL arguments.
Importing Lists of Translations
Instead of separately defining each translation, you can click the Upload list icon (at the bottom of Figure 3-19) to import a file containing a list of translations. The dialog shown in Figure 3-21 appears.
Figure 3-21 Upload Custom Dimension Translations
Use the Browse button to locate and select the required file. Optionally, use the File encoding menu to specify the file's character encoding. For more information on international character set support, see Appendix B. If an unsupported encoding is encountered, or the transcoding fails, an error is reported.The file may only contain one translation per line, with source values and translations tab separated. When ready, click Merge.
Note:
You can also use the custom dimension facility to redefine the functionality of standard dimensions.Fallback Values Reported For Custom Dimensions
Within custom dimensions, two fallback values can be reported:
None: indicates that the source defined for the custom dimension was not found within the page or function call.
Unknown: indicates that the defined source was defined after the cited period for the page or function call. For example, if a custom dimension is defined at 1 PM on a Monday, the daily view will show "unknown" for the period before 1 PM. Summarily, on the week and month views, it will be reported for the period before the custom dimension was defined.
To remove a custom dimension, do the following:
For application-based dimensions, select Configuration, then Applications, and then Custom dimensions. For function-based dimensions, select Configuration, then Services, and then Custom dimensions. A list of the currently defined custom dimensions appears. Right click the required custom dimension, and select Remove from the menu.
If the custom dimension is used as a filter in a KPI or a report, you are warned that deleting the custom dimension also results in the deletion of the associated KPI or report. Click Yes or No.
Session diagnostics provides a powerful facility 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, hits, and functions on sessions, the full content of each failed page, and the relationship between objects, pageviews, and sessions.
When problems are identified, session diagnostics 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 obtain direct insight into possible causes.
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.
Important:
By default, the error recording facility is disabled. You must enable it before error message information is recorded and available through the Session diagnostics facility. The procedure to do this is fully described in Section 8.5, "Enabling and Disabling the Error Recording".Understanding Session Reporting
It is important to understand that sessions within the Session diagnostics facility are not reported in the same way as they are in the All sessions group. Sessions are only reported in the All sessions group when the session is considered finished, either because the user has been inactive for longer than the defined session idle time (by default, 15 minutes), or the session has lasted longer than the defined session flush time (by default, 60 minutes). The use of these settings is fully described in Section 7.4.4, "Controlling Session Reporting". In addition, sessions are reported for each application that a user visits.
In contrast, information about a user session is reported within the Session Diagnostics facility regardless of the events described above, and are called user records. Because these session-terminating events are not taken into account when reported user records, it can happen that there are more sessions reported for a particular user session in the All sessions group than in the Session Diagnostics facility. For example, consider the scenario shown in Figure 3-22.
The user's activity from 08:00 until logging off at 17:00 is recorded within the Session diagnostics facility as one user record, starting at 08:00, and finishing at 17:00. Within the All sessions group, this same user activity is recorded as three separate sessions.
Understanding the Effect of Different Time Resolutions
It is important to understand that information within the Session Diagnostics facility is reported using two different resolutions. The session information available via the Info option under Content uses 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 five minute interval. Note, while the value of these properties can potentially change during the five minute period, it is their values at the end of the period that are reported.
The session information displayed within the Info option under Session (shown in Figure 3-25) is derived from the All sessions group. Within this resolution, a visitor session is assumed to last no longer than the defined session flush time (by default, 60 minutes). See Section 7.4.4, "Controlling Session Reporting" for more information about the use of this setting. Therefore, discrepancies (such as different user IP addresses) can occur between these two resolutions.
Using the Diagnostics Facility
To locate the diagnostics information you require, do the following:
Select Browse data, and select the group from which you want to start. Diagnostics information is available from within the All sessions 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, Page diagnostics or URL diagnostics. A diagnostics panel similar to the one shown in Figure 3-23 appears.
Use the Calendar controls (described in Section 2.4, "Using the Calendar") to select the required period. The selected viewing range should be a single day (or less). If you attempt to search outside this limit, an error is reported. By default, session information is only available for seven days prior to the current date. The availability of replay content is determined by the associated Collector retention policies (described in Section 9.6.2, "Defining Collector Data Retention Policies"). When ready, click Search. The results of the search are shown in the main part of the window. An example is shown in Figure 3-24.
You can 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, or use the search facility to further restrict the displayed list.
To use the search facility, specify a search pattern, and click Go. The specified search pattern must refer to the user's IP address or (in the case of the sessions and pages) to the user's ID. Note the search's scope is restricted to the currently displayed user records, the search uses partial matching, and the use of wildcard characters (such as *) is not supported. All characters are treated as literals. You can also use the extensive search capabilities available within the View selection facility.
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 buttons under the Session part to view information concerning specific aspects of the selected user record. An example is shown in Figure 3-25.
The overview shows the pages (and their times) recorded within the selected user record. Icons indicate their loading satisfaction, whether they are transaction or key pages, and whether replay content for them is available.
In the case of failed pages and URLs, the content of the selected page or URL can be viewed by selecting the Source option under the Content part of the panel. This includes both the full request header and content, and the full response header and content. The underlying HTML code of the message received by the client is also available. Note the availability of request header information can be controlled (see Section 8.5, "Enabling and Disabling the Error Recording" for more information). An example is shown in Figure 3-26.
Figure 3-26 Example Error Page Source Details
Detailed application, session, server and metric-related information about the page or URL, is available via the Info option under the Content part of the panel shown in Figure 3-25. In addition, you can click the View in new window (replay) item to view the response content of the message in a separate window. An example is shown is shown in Figure 3-27.
When ready, you can click the Remove icon beside the selected user record. You are returned to the diagnostics window shown in Figure 3-24. From here, you can select and drill down into other user records.
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
