RTI performance metrics are associated with several different kinds of RTI resources, each representing different levels of detail.
Below we have expanded the RTI Installation resource to show the RTI Enterprise installation on v-ngi2.
Expanding the RTI Enterprise resource will reveal the RTI Collector resources, which are defined for each application that RTI is enabled to monitor. There will be different RTI Collector resources for each JBoss server configuration, each Tomcat installation, each Java test client, JMeter, and so on.
Here we have revealed the RTI Collector resources jmeter and jboss_hotel, representing the JMeter script runner and the JBoss 'hotel' configuration we are testing. In the Summary tab of the jboss_hotel resource, you can see RTI performance metrics for the RTI collector. The RTI Events metric tracks the number of deep dive events that have been traced; normally this remains constant until you request a deep dive trace manually or via an alert. The other three metrics, Average Response Time, Total Transactions, and Total Failed Transactions, indicate the performance of transactions (or requests) monitored by RTI. These performance metrics indicate the throughput of the application being monitored. The RTI transaction performance metrics will only be available for collectors that monitor applications that receive requests (such as JBoss and Tomcat).

Note

You must create the RTI collectors before importing them by either exercising your application with RTI enabled (which implicitly creates the collectors if needed) or by explicitly creating the collectors using the RTI Console, as described in Section 1.3.3, “Enabling Your Applications for Monitoring”.
Expanding the RTI Collector resource will reveal the RTI Transaction resources. RTI Transaction resources are only available in collectors that monitor requests (JBoss, Tomcat and Fuse, typically). The metrics associated with the RTI Transaction resources are summarized in the RTI Collector resource.
Here we have revealed the RTI Transaction resources for the jboss_hotel collector. We see individual RTI Transactions resources for HTTP request URLs, JMS destinations, and JDBC connections in this example. Other configurations would show EJB calls, webservice request URLs, ESB messages, and so on. Each RTI Transaction resource provides the same RTI performance metrics described above for the RTI Collector resource (in the Summary tab). In the case of RTI Transactions, the metrics will only include requests of the given type, while the RTI Collector metrics total all the all RTI Transaction metrics. The RTI Transaction performance metrics can be used to track the throughput of individual request types.
A very useful summary of the performance of RTI Transactions can be displayed by selecting the RTI Transaction group folder of an RTI Collector resource.
Here we are displaying a summary of the call times of all the RTI Transactions in the jboss_hotel collector. Only active RTI Transaction resources will be listed in the table. In this example only the Seam Hotel requests are currently active (being exercised) along with some background JBoss JMS destinations and JDBC connections.


loading table of contents...