Analyzing sessions

The session viewer tab allows you to step inside of a conversation and inspect everything that took place during the conversation. The session viewer has multiple use cases, you can use it to quickly see requests and responses, the ability to step inside of a transaction to inspect the events that occurred during the transaction. For example, analyze a session and build a query around any identified problems, then do more quantitive research on your stored sessions to see if this is a reoccurring problem using the query tab, or vice versa.

Step inside a conversation

To step inside a conversation, open a session view tab and press run query. If you are looking for a specific session you can use session constraint, for example == “sessionId”, just replace the string, sessionId with a real ID. You can also use the order function to limit the results, get sessions, based on transactions, etc. The returned results will be displayed in the session list. The list provides general information about the session. 

session tab annotated

A session consists of transactions which consists of events. A transaction is a request that is sent to the engine(bot) and a response from the engine. An event is what the engine did when between processing the input and generating the output. You can expand and collapse a transaction to see its events, and you can expand and collapse an event to see all of the properties of that event.

In the video below, we are going to first construct a query to find session IDs where a resume prompt was activated but dropped immediately, then inspect the conversation in the session viewer tab:


It is possible to refine the displayed data by using the ‘Find’ and ‘Filter’ buttons, however, it is not possible to filter or find values:

  • Find keeps all events visible, and navigates you to view the next instance of what you have selected;
  • Filter removes all events that are not in the selected property list, and navigates you to the first one.

Was this page helpful?