You can create monitors and use them to collect network information and system performance data during load testing. Monitoring metrics can be overlaid onto load test results to help you determine whether the load passed to the Web server is being handled as designed.
In this section:
A performance monitor for Oracle Service Bus (OSB/ALSB) is available. Contact technical support for details.
You can add the following built-in monitors.
Adding SNMP Agent Monitors
Load Test can retrieve data based on the provided OID(s) from the SNMP agents of versions 1 and 2c.
To add an SNMP agent monitor:
Adding Windows Performance Monitors
To add a Windows performance monitor (functionality which is only available if you have a Windows installation of Load Test):
Adding WebSphere Monitors
Before adding a WebSphere monitor, go to the Security> Global security section of the WebSphere Administrative console and ensure that the Enable administrative security check box is unselected.
To add a WebSphere monitor:
Adding WebLogic Monitors
To add a WebLogic Monitor:
Adding JBoss Monitors
To add a JBoss monitor:
Adding Tomcat Monitors
To add a Tomcat monitor:
Adding rstat Monitors
To add an rstat monitor:
Adding Remote JVM Monitors
To add a remote JVM Monitor:
Adding Custom Monitors
To add a custom monitor:
After a monitor has been created, you can set or modify the Apply Operation parameter for the following built-in monitor types:
To modify the operation, double-click the monitor channel in the Parameters panel of the monitor configuration view and set the appropriate operation type and value.
Load Test allows dynamically adding monitor types to the Load Test installation. Deployed monitors are displayed in the Deployed monitor types table of the Performance Monitors wizard.
Adding AppDynamics Monitors
To add an AppDynamics monitor:
Monitoring Data Available from AppDynamics Monitoring Extensions
The AppDynamics Exchange site offers a number of Monitoring Extensions. Monitoring Extension data available in AppDynamics Metric Browser will be available in the Load Test AppDynamics monitor.
The screenshots below show the data exposed by the ‘Static’ Monitoring Extension available from the Exchange in the AppDynamics Metric Browser View and the Load Test AppDynamics monitor channel selection view.
Custom FileContentMetric in AppDynamics:
Adding Dynatrace Monitors
To add a Dynatrace monitor:
The monitor channel selection view tree is structured in the following way:
You can monitor either existing Chart Dashlets of Line Chart type or create new ones. You can add multiple Measures (data series) to a Chart Dashlet. See the Dynatrace vendor documentation for more details.
Dynatrace REST Query Response Size Considerations
The sizes of the Dynatrace REST responses can be quite large (100KB and more), depending on the Chart and Dashboard configurations.
To minimize the size of the Dynatrace REST query responses:
Monitoring Data Available from Dynatrace Plugins
The Dynatrace ‘PLUGIN CENTRAL’ site and ‘Community Plugins and Extensions’ site contain a number of plugins, many of which can be used to extend the out-of-the box Dynatrace monitoring capabilities. The Dynatrace plugin data added as a Measure to a Chart Dashlet will be available in the Load Test Dynatrace monitor.
The screenshots below show a StockQuote sample monitor plugin available from the ‘Community Plugins and Extensions’ site added as Measure in a Dynatrace Chart Dashlet and in Load Test Dynatrace monitor channel selection view.
Custom StockQuote Measure in Dynatrace:
Adding Remote JVM Threads Monitors
The JVM Threads Monitor allows you to observe threads statistics, as well as record individual thread details of a remote Java application using Java JMX technology.
To add a Remote JVM Threads Monitor
About Channel Descriptors
All data returned by monitor channels is related to the last Load Test data collection interval.
The NEW, RUNNABLE, BLOCKED, WAITING, TIMED_WAITING, TERMINATED are the states from the
For details about JVM thread states, see the Java documentation for relevant Java classes:
Upon initialization, the JMX Threads Monitor checks if thread contention monitoring is enabled on a remote JVM. If contention monitoring is disabled, the JMX Threads Monitor attempts to enable it. If this attempt fails, the BlockedTime, BlockedRatio, WaitedTime and WaitedRatio channels will return zero values.
Taking Selective Thread Dumps
The JMX Threads Monitor allows you to take selective dumps of a remote application's threads and save them to disk for further analysis. This feature helps you catch undesired thread states that appear sporadically or record thread states during the automated load test runs.
The JMX Threads Monitor will only dump threads when a load test is running. Thread dumps will not be taken when clicking Send Request in the monitor configuration view.
Set the following monitor properties to configure selective thread dumps.
Examining Thread Dumps
The path provided in the Thread Dump Directory setting will be used as a thread dump root. The JVM Threads Monitor will create a separate project thread dump directory under the thread dump root for each load test run. These project thread dump directories will have the following name pattern: PROJECTNAME_YYYY-MM-DD_hh-mm-ss.
This format allows you to clearly see which Load Test project a thread dump is related to and when it was created. The PROJECTNAME_YYYY-MM-DD_hh-mm-ss directory will not be created if the monitor does not find threads to dump that match the threads dump configuration during a load test run.
The monitor will create thread dump files with the following name pattern inside the project thread dump directory: S..S_hh-mm-ss.txt
Each thread dump file will contain one or more thread stack traces taken by the monitor. A thread stack trace will have the following format:
Each BLOCKED thread will be followed by a stack trace of the thread that is blocking it. A BLOCKED thread output will have the following format:
Matching Thread Dumps to Graph Points in the Load Test Report
To find a thread dump for a particular point in the Load Test report graph follow there steps:
For example, the 3_10-37-37.txt file will be the thread dump file for the graph point highlighted in the screenshot.
Once some parameters have been added to a monitor, they can be queried.
To send a query:
Query results will be displayed in the Response View area of the monitor’s configuration panel.
The Load Tests tree uses color bubbles to indicate the status of each monitor. The following colors are used:
To verify the current state of one or more monitors:
The monitors that you have added to the Load Tests tree will be used during test suite load testing.
During a load test that uses monitors, Load Test adds a bar for each monitor within the Graph tab of the Load Test Progress panel. The Graph tab displays data collected from the monitors. The names of these bars are based on the monitors’ Graph Title values, not by OID numbers or parameter IDs.
Monitor data collected during load testing is saved in the Detailed Report, where it can be viewed together with and correlated to the default data (such as "Number of Virtual Users", etc.)