• When request data is captured in events, you can search for the data through the Portal.
• Additionally, the data is available for reports created through the Report Builder.

The following steps provide a general approach for how to capture request data into event objects for search and reporting purposes.

1. Identify the request data to capture:
   • As an example, search for data that fits the following pattern:

     
     HTTP_X_TEALEAF_PAGE_CUI_EXCEPTIONS=2
     

   • The value to the right of the equals sign is the one to capture and can change with each hit.
2. Create the hit attribute: Through the Event Manager, you must create the hit attribute to look for and capture, if present, this data on each hit. Key properties:
   • Define the hit attribute to check the request.
   • Start Tag:

     
     \r\nHTTP_X_TEALEAF_PAGE_CUI_EXCEPTIONS=
     

   • End Tag:

     
     \r\n
     

   • Verify that it is not a case-sensitive search.
3. Create the dimension: You can also create a dimension sourced from the hit attribute to capture the contextual information. Key properties:
   1. Populated By: Select the hit attribute that you created.
   2. Populate With: Select the First Value on Page/Hit.
   3. Values to Record: Select Whitelist + Observed Values.
      Note: When observed values are allowed to be recorded, data is immediately collected and available. However, every instance of the dimension is recorded without limit to the number of instances. Wherever possible, dimensions that record observed values should be converted to whitelist only dimensions.
4. Save the dimension.
5. Commit the changes to the server.
6. Create the event: Through the Event Manager, you can create the event to be triggered off of the hit attribute. The event records the value of the hit attribute. Key properties:
   • Evaluate: Every Hit
   • Track: Every Occurrence
   • Value Type: Numeric
   • Condition step:
     • Select the hit attribute you just created. If you did not specify a label for it, it is under the Default label.
     • Set the condition to be Hit Attribute Found and Is true, since this value is not inserted when there are not exceptions.
   • Value step: For the item to record, select the hit attribute you created, which means that the numeric value of the hit attribute is recorded as the numeric value for the event.
   • Report Groups step: If you wish to have the event associated with any contextual information, you can associate report groups containing the contextual dimensions in this step. It is not a required step.
   1. Save the event and hit attribute.
   2. Commit the changes to the server.
7. Test the event: To test the event, you can send sample sessions, which include the data, to the Event Tester.
8. Allow event counts to accumulate: If the event and hit attribute are properly firing in the Event Tester, you must let sufficient time to pass for occurrences of the event to be detected in the Canister and stored in the reporting data.
   1. While you are waiting, you can search for the event through the Portal.

      You should be able to search for active sessions that include the event as soon as it is detected in the Canister.

   2. After sufficient time has passed, you can create a report using the event. If you created the dimension, you can use it in reports, too.