When you open search, you can specify the criteria with which to search session data.

• The search query can contain up to six parameters.
• You can also search active sessions by using a reduced set of query parameters.
• More detailed search criteria can be specified through the Advanced Search tab.

The set of sessions that are returned by Search Server is called the search session segment. This list of sessions is displayed in the Session Segment pane.

• The search session segment can include sessions from each searched cxImpact server.
• The maximum number of sessions that are returned by each search server is configurable by each RTV user.

Sessions that are loaded into RTV and displayed in the Session Segment pane can be searched with the Subsearch tool. You can search for any arbitrary text in the Request or Response blocks of a search session segment by using the Subsearch tool. It can be used to examine all name-value pairs found in the selected sessions for specific combinations.

• RTV limits any single search to a maximum of six search terms.
• All defined Tealeaf events are listed and can be added as search terms.
  Note: To limit index size, indexed words are truncated to a maximum of 32 characters each. Longer words are truncated at 32 characters to match search terms in the index and are submitted without prompting the user. Tealeaf administrators can change this limit through the configuration options of the Index Service configuration.
• If auto merge of fragments is enabled, using the NOT option can display improper results. If searching the session for the absence of a search term returns a true result and a related fragment of the session returns a false result (meaning that the term is present in the fragment), both the session and the fragment are listed in the results, even though the term is displayed in the fragment. Avoid using the NOT operator when sessions are fragmented.

  In general, searches using Boolean search terms can be applied to a single session fragment only, as the underlying search engine is unaware of fragmentation. If the session contains multiple fragments, search results can be inaccurate. Through RTV, you can retrieve search results for one search term and then complete a sub-search of the returned sessions on the other term.

• When you search for URLs, remove the following punctuation in the URL:
  • colons (:)
  • question marks (?)
  • equal signs (=)
  • ampersands (&)

Binding search terms

You can define how the search terms are combined by using the Search Builder tab.

Search terms can be combined in the following ways:

• The AND binding is used to find all search terms that are displayed in the same session. To appear in the results, Search terms can appear on different pages of the session. A page must contain all search terms that are combined with AND.
• The OR binding is used to find all combinations of search terms that are displayed in the same session. If a page contains any of the search terms, it is displayed in the search session segment.
• You can specify all search terms that must be displayed on the same page of the session using the And on Same Page (AOSP) binding.
  • You cannot use the NOT operator in search terms for an AOSP search.
  • AOSP Binding is not available on the Advanced Search tab, only on the Search Builder tab.

RTV handles the AOSP request by issuing a search request to the Search Servers specifying all search terms combined with AND in the session. Each returned session has all of the terms somewhere in the session fragment. The Search Servers return the maximum number of sessions to return. RTV examines each returned session and discards those sessions that do not have all of the search terms on the same page.

This two-step search process requires careful construction of your queries. Build your query to find the true subset of events on the same page, so that AOSP does not have to weed through many irrelevant sessions.

The Max Number of Sessions Returned setting affects this feature. Since the Search Servers can return no more than the maximum number of sessions, the results can be just a subset of the complete set of matching sessions. That subset may not include any session fragments with all terms on the same page, even if they exist.

Subsearch

After a search returns a set of sessions that match the search query, you can search within that set using Subsearch. Subsearch can complete simple searches to look for specific values in individual fields. To find specific values, RTV must scan the set of returned sessions to create name-value pairs.

If the search results contain many records, this process can take a while; start with small SubSearch tasks first. When the SubSearch completes its search, the SubSearch dialog is displayed. You can enter the name-value pairs retrieved in the executed search.

• The leftmost column contains drop-downs of the available fields to search. This set of fields is a superset of the indexed fields available for searching.
• The middle column enables the selection of the search constraints on the field.
• For the selected field, the rightmost column contains the list of available fields.
• You can specify how the terms are logically bound together: AND, OR, or AND ON THE SAME PAGE using the Operator drop-down in the upper right of the SubSearch Search dialog.

Search syntax

The syntax for the search terms is straightforward. All search terms are not case-sensitive. Search terms can be grouped by using parentheses.

Keywords

This setting finds a list of words or phases that match any or all of the terms.

• Use quotation marks (") around phrases
• Add + in front of any word or phrase to require it
• Add - in front of any word or phrase or to exclude it

banana pear "apple pie"
"apple pie" -salad +"ice cream"

Boolean

This setting finds a structured group of words or phrases that are linked by and, or, not, and w/.

Special characters

This setting finds special characters that match the search terms.

Weights

By default, all words in a request are counted equally in search results. You can change this weighting by specifying the relative weights for each term in your search request.

Variable term weighting allows the weight of each search to be specified in the search request. When results are returned, they are stored based on the weights. For example:

apple:5 and pear:1

The preceding request retrieves the same documents as the search apple and pear. However, the search engine weights apple five times as heavily as pear when it sorts the results.

You can apply weights to the following Boolean search terms:

(description:5 contains (apple and pear)) or 
(author:2 contains ("John Smith"))