To enable improved search performance, Tealeaf scans completed sessions for a predefined set of data that is typically of use in locating sessions. The Portal and RTV then use these indexes to quickly locate sessions based on search criteria that you enter. For many customers, this dataset is sufficient to enable effective search for sessions of interest.

Indexes are not used for searching active sessions. In some cases, you may decide that some session data that is not available for search by default should be accessible, for example:

• You have created pipeline rules that insert application-specific data into the request.
• You have deployed CX UI Capture for AJAX, which enables the capture of user interface events from the visitor's browser.

  In the above circumstances, the data may not be automatically indexed for search. Using one of the provided methods, you can make this data available for search through indexed data or event values. Using privacy rules, you can move data from anywhere in the response or the request into the [appdata] section of the request, where it is automatically indexed for search.

  Note: Adding index data is considered a Tealeaf administrator task. Adding data to be indexed for search increases the size of the indexes stored in the Processing Server. Depending on the volume of increased data that is marked for indexing, indexes can grow considerably and may impact available disk space and performance of the Processing Server. Before you begin adding data, you should review your goals with IT staff.