After the search has completed, a list of matching sessions is displayed in the Session List page.
Fields that have been encrypted using privacy rules in the CX Passive Capture Application or Windows™ pipelines, cannot be decrypted in the Portal. Instead, encrypted fields can be decrypted only during replay. As an alternative, you can leave the configured fields in unencrypted state in the session data and then define privacy rules specifically to be applied during session replay, permitting the display of the unencrypted data in the Portal, as needed.
Displaying a session list at the page level
You can display a session list at the page level and then analyze the details of the pages that are displayed.
Displaying a session list at the page level can make it easier for you to focus your analysis on the page level data within a session.
To display a session list at the page level:
- From the Session List page, click the Page List icon of the session for which you want to display pages.
A Session Summary section is displayed. The pages in the session are displayed below the Session Summary section.
Note: Events that have theDisplay in Session List
setting disabled are not displayed in the Page List. - Review the Session Summary section.
The following table explains the data that is displayed in the Session Summary section:
Table 1. Session Summary data Field Description TLTSID Session identifier. Page Count Total number of pages in the session. Note: Hits captured from the client user interface through one of the Tealeaf logging frameworks are not tabulated in this metric.Total Events Total number of events that are found in the session. Connection Type The type of connection (DSL for example) used for the session. Avg Round Trip Average time between start of the response to the end of the request. Avg Network Trip Average time for hit and response to travel across the network. Session ID The internal identifier that is indicating where the session is stored in the Canister. Session Start Displays the time when Tealeaf began recording the session in the short-field canister. Duration Specifies the length of the session in minutes. Avg Page Gen Average generation time in seconds. Avg View Time Average view time in seconds. - Review the information pages that are displayed.
The pages are displayed in the order in which they were encountered by the visitor.
The following table lists the grid headings and explains the contents for headings.
Table 2. Page List headings Field Description Page Specifies the number of the page in the sequence of the session. The page number for each page is a link to drill down into individual page views.
Events Displays the icons that are representing the events that occurred on that page. URL The URL address of the page. Status The status code that is generated by the web server for the page. RT Time Round-trip time for the request and response. The time from the first byte of the request coming in to the last byte of the response going out. Net Time Network time is the number of seconds required to receive the request and transmit the response. Gen Time The time that is taken by the web server to generate the page. View Time The length of time the visitor remained on the page. Size The size of the response in kilobytes. - Optional: To see the query strings that are used to run the search, click the Show query strings check box.
- Click the Page number link to display the details of the page.
The page detail view contains information about the individual pages in a session. The Page Details table describes the sections in the Page Detail view, each of which can be expanded or collapsed by clicking the section's header.
Table 3. Page Detail sections Section Description Hit Details Page number, hit number, and session ID. To replay the session, click the session identifier
[iamie] The unique IDs associated with the hit and session, as well as capture information. [env] Environment variables from the request and the response. [timestamp] The timestamps and time ratings. These values are specified by the passive capture application and do not reflect time values for the web server or visitor's browser. [urlfield] The data that is contained in the URL field area of the request. [headers] The data that is contained in the response headers. [cookie] The cookies that were sent with the request. [appdata] Extra data that is associated with the hit, which can also include configurable fields. [ref] Contains reference data that is inserted into the request. Typically, this section is empty. [response] The raw response content of the hit.
Viewing page events for a session
You can use the QuickView command icon to view information about which events fired on each page on a session, and to view the dimension values recorded with the events.
The view provided by the QuickView command icon lets you see the details on the triggering of each event in the session.
To view the page events for a session:
- From the Session List page, find the session and click the QuickView command icon.
Note: For sessions that do not contain at least one standard request and response, QuickView data might not be displayable.
For the selected session, information about which events fired on each page, and the dimension values recorded with the events is displayed.
Events must be configured to be displayed in the Portal and to be displayed in a session list.
Events that are provided with cxOverstat are not displayed in a session list.
Note: If you cannot see events in QuickView, select theAll Events
option from the Event Label drop-down. Events that have theDisplay in Session List
setting disabled are not displayed in QuickView at all.Note: If you deploy one of the Logging Frameworks from CX Mobile for Mobile App, QuickView contains no data. The pages captured from any supported Logging Framework do not contain viewable data.If you deploy UI Capture, user interface events are displayed on the last valid page on which they fired.
- Review the QuickView information displayed.
- To view details for a page, click the page number link in the left column.
- To control order of the data displayed on the page, select an option from the Order By drop-down list.
Hit Number
- events and dimensions are listed by the sequence that is determined by the hit number. The events that fired on a hit are ordered by the hit number.Event Name
- events are listed in alphabetical order. For each listed event, you can see all of the pages on which it fired.
- To select a different event label whose events you want to see in the event list, click the <Add Label> link.
To see all events that fired in the session, select
All Events
. - Select the Show Dimension Constants check box to include in the list dimensions where constant values such as
[Limit]
,[Others]
, and[Empty]
were recorded.To display dimension values that contain non-constant data from the capture stream, clear the Show Dimension Constants check box.
- Click Email to email the selected session to a comma-separated list of recipients.
- Click Replay to replay the session in CX RealiTea Viewer or Browser Based Replay.
- To review the dimension values that were recorded when an event was triggered in the session, click the Plus (
+
) icon next to the event name.On individual lines, each dimension and its recorded value are listed.
To normalize values or place limits on the volume of data that is stored, Tealeaf supports a set of dimension constants. These constants can be inserted as dimension values when actual data is not available or exceeds allotted storage space. Constants such as
[Null]
,[Others]
,[Limit]
, and[Empty]
are displayed in place of detected values in these situations.
Sending sessions to the Event Tester
You can send any session in the Session List page to the Event Tester for use as test data against events in development.
In a session list, you can move the mouse over an event icon to display a tooltip that identify the name of the event. So, you can locate events that you are testing using the event tooltips and then send the event to the Event Tester as sample data.
Complete the following steps to send a session to the Event Tester:
- From the Session List page, locate the session that you want to send to the Event Tester.
- Click the Send to Event Tester icon next to the description of the session.
- In the Send Session to Event Tester dialog, enter a description or accept the default.
The default description is the session ID.
- Click Send to Event Tester.
A message indicating that the session was successfully loaded for the Event Tester is displayed.
- To go to the Event Tester, click OK.
To return to the session list, where you can add more sessions to the Event Tester, click Cancel. The event that you sent is still available in the Event Tester.
The sessions that you send to the Event Tester can be selected and used to test against some or all available events.
Providing a Search URL to Portal users
You can use the Link to URL command icon to access the Search URL and provide that URL to Portal users.
- From the Sessions Search page, click the Link to URL icon in the Search toolbar.
- Copy the URL from the Search URL window.
- Provide the URL to Portal users.
Note: This URL does not run the specified search. When this URL is selected, Tealeaf users must still authenticate through the Portal. Tealeaf does provide an external API for running through code specified searches.
Exporting session data
Through the Session List page, you can download the list of displayed sessions to several formats for active, completed or all searches.
The exported session list includes all columns of the session list, as well as links for replaying sessions in BBR or RTV.
To download the displayed set of sessions from the Session List page:
- Click Download All.
- Optional: Change the session list display limits.
The number of sessions displayed in the session list is configured by a set of parameters depending on the type of session:
- Active Sessions - Configure the
Live Max Results Limit
parameter setting to define the number of sessions. - Completed Sessions - Configure the
Session Segment Max Sessions Limit
parameter setting to define the number of sessions that can be displayed in a session segment.This limit also applies to cxReveal searches.
- All Sessions - A single All Sessions search executes one search for active sessions and one search for completed sessions, so the maximum number of sessions displayed in a segment is the sum of the above two parameter settings.
Note: The actual number of sessions displayed may be reduced by the applied session list template. - Active Sessions - Configure the
- Optional: Change the columns to be exported
You can configure a session list template to display other fields. For example, you may wish to insert session attributes as columns in the session list template. These values can then be exported for third-party analysis.
For data export purposes, you may wish to create a separate session list template to export session data. Or you can modify your existing session list template, as needed.