JMeter monitoring allows running JMeter scripts at predefined intervals of time.
Apache JMeter is an open source testing software. It is 100% pure Java application for load and performance testing.
JMeter is designed to cover categories of tests like load, functional, performance, regression, etc, and can be used to test performance both on static and dynamic resources like Web dynamic applications.
It can be used also to simulate a heavy load on a server, group of servers, network or object to test its strength or to analyze overall performance under different load types.
Apache JMeter requires JDK v 8 or higher.
Please refer to JMeter documentation for more info.
JMeter monitor supports HTTP/HTTPS GET/POST requests for Apache JMeter basic package (tested for versions 2.1 – 3.2).
Script Review Process
To avoid possible abuse of the service, JMeter scripts added by in-trial users will be reviewed by our Tech Support within 24 hours before they are allowed to run. If no threat detected, the script will be enabled from our side. Otherwise, the scripts will stay blocked and you will receive an email.
JMeter monitor runs JMeter scripts from our globally located servers and shows the results.
You can use JMeter monitor as an API monitoring tool to monitor execution of API actions that you have coded in your JMeter script.
Important: note that currently JMeter monitor supports only running scripts that do not contain coding that interacts with GUI elements.
Adding JMeter Monitor
To add a JMeter monitor go to the Monitors top menu and select Application Monitors -> JMeter.
The Add JMeter Monitor window will open.
To upload your JMeter script click Browse and select the file. Note that there is 1 MB limit on the script file size.
Under Timeout (sec) enter the amount of seconds that if elapsed your server will be considered not responding. The request will be then aborted.
Enter a name for the monitor.
Set the check interval by moving the slider. Currently 15 min is the highest available check frequency.
Select the location to run the script from. Currently, you can select only one location.
Click Add when finished.
The Alert Configuration window will appear.
- Click Send to All Contacts if you want to send alerts for this monitor to all contacts.
- Click Custom Configuration (Advanced) to configure sending alerts for this monitor only to selected contacts.The Alert Rules window will open. Click on the Add Alert Rule button to configure alert rule(s) for your monitor.
Set up the alert rule and click Add Rule. See Alert Rules in Alerts 2.0 for more info about alert rules.
Note: To be able to add alert rules, you need to set up thresholds (Critical or Warning) in your monitor first.
A threshold includes two conditions connected by a logical OR. If any of the conditions matches the monitor will enter your specified state.
- Check fails (response timed out, connection failure, etc)
- Any or all of your selected metrics meet the failure conditions you specified for them
See Thresholds for more info.
Viewing JMeter Monitor Data
In the table view you can see:
– Latency (ms) – Total time it took to execute the JMeter script.
– Success flag – True if the script was executed successfully, false if script execution failed.
If you double-click on any row, you can see all the steps coded in the script, with Latency, Success Flag and Response Message and request volume (Bytes) shown next to them.
Clicking on a step will show the response details.
You can switch between the tabs to view the sampler result, requests and response data.
If you switch to the Chart view, you can see Latency data plotted on the chart.
You can use the monitor’s Settings for viewing and changing the monitor’s configuration.
Under the General tab you can upload a new script file for the JMeter monitor.
Under the Monitoring Locations tab you can change the monitoring interval (15 min by default).
- Currently, the monitor supports only scripts that do not contain coding that interacts with GUI elements.
- Response data size <= 2,000 symbols – data above this size will be truncated.
- JMX file size <= 1 MB.
- Script execution time <= 5 min – if timed out the check will be aborted.
- Resource limitation can be applied in case too many resources are consumed by the monitor, in which case the check will be aborted.