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 style sheet, 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.
Now let's use the Deep Dive tree to drill into the poorly performing Transaction. For any Transaction where RTI has collected sub-Events, like network requests for images, CSS files, etc., we can use the Deep Dive tree to see each Event and identify why the overall Transaction was slow. Lets select rtiperformance.com in the tree, and then expand it by selecting the usual [>] or [+] icon to the left of the IE icon, depending upon your console platform. You can also double-click on the row, or right-click to see the context menu of operations and choose Focus on Selected 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.

loading table of contents...