Searching for Dialogs in OCP® Monitor

Use the OCP® Monitor search filter to find dialogs by ID, date range, application layer, or advanced criteria.

Search Filter

The search filter allows you to restrict and refine the dialog search according to the selected criteria.

It is possible to search for all the dialog sessions that match the selected criteria or to select one particular dialog session.

• For a quick search, select one of the Search by criteria and paste its ID into the ID search field:

  • Dialog ID

  • Session ID (Available only for Virtual Agent)

  • Connection ID

• To search for all the dialog sessions that match the selected criteria, choose the criteria and click the Apply icon.

Application Layer

Application Layer allows you to view full end-to-end conversations only without the subcomponents, providing a clear high-level overview of each dialog in OCP.

Once the Application Layer is activated, you can expand each Dialog Application and view its components by clicking the dropdown icon. However, if you apply the Search by filter using either Dialog ID, Connection ID, or Session ID, the hierarchical structure will not be displayed.

Date Range Filter

You can set your search within a specific Date/Time range using the Date Range filter. Set the Timezone, start and end dates, and start and end time, or select a specific time range to date, for example, Last 48 hours.

Advanced Search

To open the Advanced Search filters, proceed as follows:

1. Select the Agent Type.
   

   

   
   

2. Click on Filters button.

3. The Advanced Search area opens.
   

   

   
   

4. Select the search filter fields. In the table below, you can find detailed information on each field.

5. To submit your search request, click the Apply button.

6. Go to each filter and add the required value or select from the drop down list.

   

7. The dialogs that match your selected criteria are shown in the Dialog list.

Applied filters are indicated below the Filters bar

Search Filters Description

Initial filters available in the Default Filters area include:

The following filters are available upon clicking the Filters and selecting specific type of agent:

Text Matching

We use a Standard Text Matching analysis to process step’s prompts and utterances and an Events Matching Approach for dialog events. Both of them use a list of terms parsed from the text instead of the whole text, but in a different way to ensure the best accuracy.

The Standard Text Matching analysis:

• matches all the words of the given text;

• does not care about the words’ order;

• matches all the given words anywhere in the text;

• case insensitive.

Example

This text:

Welcome to our new voice-enabled service line. I'll be your Virtual Assistant.

will have the following matches:

• “welcome” (single word match)

• “welcome to our new“ (all words match)

• “Welcome” (case insensitive)

• “Welcome to our...” (ignores trailing punctuation)

• “assistant service Welcome” (ignores word order)

and will not match the following:

• “Hello welcome to our” (not all words match)

• “come” (any random substring won’t match)

The Events analysis:

• matches all the words of the given text;

• cares about the words’ order (to avoid wrong matches, due to events string format);

• matches consecutive words (phrases);

• case-insensitive.

Example

This text:

“DialogGroupID:13188be3907c4f340d69479834b07b0a5fb64b6d.1712755163180.49a7bca9167e4d1eb1c2aceb8f3592d1,FlowName:MiniApps,appId:c958d295-9348-4899-9783-e09a5e8abcec.Card_GetAccessToken_WebService.WebService.MiniApps.ocp-qa,requestId:undefined,envMode:DEV,testMode:true,Locale:en-US,globalResult:fail:apiException,HUP:Custom FailExitReason,HUP:NEAR,endType:NEAR_HUP,billable:false”

will have the following matches:

• “DialogGroupID” (single word match)

• “dialoggroupid” (case insensitive)

• “globalResult fail apiException HUP Custom FailExitReason” (all words match)

• “globalResult:fail:apiException,HUP:Custom FailExitReason” (ignores punctuation)

• “globalResult:fail:apiException” (fail with reason)

• “globalResult:fail” (fail with no reason)

• “13188be3907c4f340d69479834b07b0a5fb64b6d.1712755163180.49a7bca9167e4d1eb1c2aceb8f3592d1” (group ID match)

• “Webservice” (other word from the list of tokens)

• other IDs or app name/org which could be found in event string

and will not match the following:

• “globalResult fail HUP FailExitReason” (words in order but not consecutive)

• “FailExitReason DialogGroupID HUP” (random word order)

• “group” (any random substring won’t match)

For an overview of all OCP® Monitor components, see OCP® Monitor User Guide.