RTI is all about the Transactions: the
browser or other enterprise interactions that you want to measure or understand
from end-to-end.
At the basic level, a Transaction is composed of one or more Events. Each Event represents a unit of work which RTI measures and then
correlates to other related Events to provide
a complete end-to-end diagnostic capability.
For example, as you navigate to different pages within IE, RTI is measuring
the end-to-end response time of each navigation; from your "click" to the time
when the page is finished "rendering." As IE loads each page, it may need to
get additional information: a picture, a stylesheet, or maybe some javascript.
All of these Events are related, and
coordinated by the browser to complete your navigation. As the browser
initiates each Event, it is captured and
measured by RTI. The total of all related Events generated by the browser make up the Transaction. RTI can track each individual
Event end-to-end, so if there is
performance problem, you can quickly find its root cause. We’ll go into more
detail below, but here’s a quick picture showing a single web Transaction, for
navigation to http://ocsystems.com/,
and a few of the Events the browser generated to serve that Transaction:
Generally when we want an overview of what's happening with our browser or
enterprise, we start by looking at the Transactions as a whole. To learn more
about a single Transaction, we’ll dive deeper and look at its individual
sub-Events.
 |  |  |
| 2.4.3. Analyzing Web Performance Data |  | 2.4.5. Deep Diving into RTI Web Events |
