Event log

The Event Log shows the events that occur when a script is executed. It contains detailed data about each event of a transaction in a sortable table. For each event, the type of event is indicated by an icon, and the time is shown in milliseconds from the start of the script execution. It also shows the Type of event, the Event Sub ID and Information about each event. Additionally, you can display the Event ID and the Execute Sequence if you would like.

The information in the Event Log varies slightly between a Transaction Perspective and an Application Perspective script. This is because Transaction Perspective uses the actual Internet Explorer browser while Application Perspective uses a simulated browser, and does not show Internet Explorer events.

Event log

Event log

The events in the Event Log for a Transaction Perspective script are grouped by Action and Idle sequence, and each can be collapsed to quickly navigate through the event log to find the event you are looking for. An Application Perspective script does not show Idle sequences.

The ID column provides a numerical identifier for each event.

The Time Sequence displays the time that each event occurred relative to the initiation of the script execution. These values are in milliseconds.

The Exec Sequence headings offer you a way to quickly view the events for each action of a script. There are two types of Exec Sequences Idle and Action . The Action Exec Sequence shows you all of the events that occur during an Action of a script. The Idle Exec Sequence shows all events that occur before and after the Actions. Anything recorded during an Idle sequence will not be reported in MyKeynote.

The Type column contains additional information about the event type. For example this row shows that the starting URL was input into the IE address bar XXXmsec after clicking the Playback button. This event shows that the network request was sent xx msec later.

Because IE supports concurrent connections, the start and end times of individual events often overlap; to address this KITE has the Event SubId column. This column contains numeric values that make it easy to identify the start and end time of an event. As you can see there are many intervening events between the begin request events for item 1 and item 2.

The Info column contains detailed information such as URLs, IE status text and the progress of the about each event as necessary.

Value of the event log

The Event Log is helpful when trying to verify that all of the content that it is important to monitor has been downloaded. This is true for both TxP and ApP scripts but the Event log is especially useful when troubleshooting completion events in TxP scripts.

Notice that the event log for a TxP script contains Exec Sequence: Idle sections between each action while an ApP script does not. This is because ApP does not utilize completion events at the end of each action and simply moves on to the next action immediately after all of the files referenced in the base page are downloaded.

On the other hand, TxP waits for programmatic cues before moving on to the next action of a script. If a completion event is not properly configured it is possible that a script will move on before the page is fully rendered. This can result in the page not being accurately monitored, or worse: it can result in a transaction failure if the element that the next action is supposed to interact with is not ready. This fact makes the KITE Event Log one of the most valuable tools for troubleshooting problems with completion events.

The most common use of the Event Log for troubleshooting completion events is to look at the Idle sequence sections and make sure that they do not contain any events except for the “begin action pause” and the “end action pause”. It is a good practice to take a look at these Idle sequences after playing back your script to make sure they do not contain any extraneous events.

Transaction Perspective events

TxP event icons

TxP event icons

Each event shown in the Event Log for TxP transactions is either

  • a KITE generated event,
  • an Internet Explorer Generated Event, or
  • an Internet Explorer Network Generated Event.
TxP event log example

TxP event log example

*Events Log for Transaction Perspective Script *

Application Perspective events

ApP event icons

ApP event icons

Events displayed for ApP transactions are either

  • KITE Generated Events, such as Begin Action, or Begin Step, or
  • ApP Browser Generated Events, such as fetching individual page elements.

ApP event log example

*Events Log for Application Perspective Script *