STS file

The STS file contains data that applies to the entire session, including the session attributes.

The following variables in the Canister Summary section are indexed.

• TltStsBrowser
• TltStsBrowserType
• TltStsCanisterID
• TltStsCloseSessionEvent
• TltStsDomain
• TltStsEnumValueId
• TltStsEventText
• TltStsEventUniqueId
• TltStsEventUniqueIdHour
• TltStsFirstPage
• TltStsFirstUse
• TltStsIPaddr
• TltStsLastUse
• TltStsLastPage
• TltStsLoginID
• TltStsNumHits
• TltStsRandomSel
• TltStsSesnDuration
• TltStsSesnID
• TltStsSesnIdx
• TltStsTLTVID
• TltStsTrafficType
• TltStsTxtPages
• TltStsUniqueIdAndEnumValueId
• TltStsUserDef
• TltStsUserID
• TltStsCustomVar0 - TltStsCustomVar63
• TltStsEventUniqueId fields are recorded in the STS file in the order of occurrence. An event is only listed once in the STS file but may be listed multiple times in the request buffers of individual hits.

Request file

[AppData] Section: Everything is indexed in this section. If you wish to index something in the request, insert it as a name/value pair in this section.

[Env] Section: Only the following fields are indexed:

• http_referer
• http_remote_addr
• local_addr
• referer
• remote_addr
• remote_host
• StatusCode
• URL

This section may be populated from HTTP request/response headers, PCA data insertion, and Windows™ pipeline actions.

[Timestamp]

The following fields are indexed:

• NT_Grade
• RT_Grade
• WS_Grade

[URLField] Section: Everything is indexed in this section.

Session Attributes

In addition to searching the response data described above, Free Text searches look for and find any of these fields in a request.

Cookies are not automatically added to the indexes. Sites that employ cookies may have multiple cookies containing long unreadable strings of encoded data on personalization information, often unique to every hit. Indexing these generally leads to extremely large indexes.

If there is a specific cookie that should be indexed/searchable, you can add it to the [IndexFields] RTA rule that copies the cookie and its value into the [appdata] section of a request, which will make it be indexed and searchable.

REQ section

For standard indexing, the following sections are indexed:

• [urlfield]
• [appdata]
• [TimeBlock] - time of the hit
• [TLFID_] section

If there is an entry of TLMergeId in the [appdata] section, put the <TLMergeId> entry at the end of the XML.

TimeBlock section: Into each request is automatically inserted the [TimeBlock] section, which contains timing information related to the hit. This data is automatically indexed.

Below is an example [TimeBlock] section:

[TimeBlock]
WEEK=24
MONTH=6
QUARTER=2
YEAR=2010
HOUR_OF_DAY=13
DAY_OF_WEEK=4
DAY_OF_MONTH=10
DAY_OF_YEAR=161

Fact section: In standard indexing, each recorded fact is indexed, if it has been configured to be searchable through the Event Manager.

Searchable=True

If this flag is true, the following elements of the fact are indexed:

• TLFID
• TLFactValue
• TLDimHash*

Example fact definition:

[TLFID_78]
Searchable=True
TLFID=78
TLFactValue=1
TLDimHash1=926515C2EE3C2BAB9D2C675E0FD8B487
TLDimHash2=C815C31FCFF0FD2640B310579BD35BCC
TLDimHash3=8CD892B7B97EF9489AE4479D3F4EF0FC
TLDimHash4=04C3451BC46213B3EAD4DCBFBF9E3389
TLDim1=/store/defaultpage
TLDim2=www.straussandplesser.com
TLDim3=store
TLDim4=63.194.158.210

In the above example, under standard indexing, the first two items and the last form items are not indexed.

TimeGrades

The following TimeGrades fields are in the XML for every hit:

• <WS_Grade> ExcellentWS </WS_Grade>
• <NT_Grade> ExcellentNT </NT_Grade>
• <RT_Grade> ExcellentRT </RT_Grade>
  Note: Other options are Normal<nn>, HighNormal<nn>, or High<nn>, where <nn> represents WS, NT, or RT, depending on the measure.

In captured data, you can search for time grades.

JSON Messages

Messages submitted in JSON format from the Tealeaf client frameworks are automatically indexed as Request/RequestBody pairs.