JMXPress documentation#
JMXPress is a performance engineering workbench. It covers the work around a JMeter run: capturing a journey, turning it into a test plan, giving that plan the load and the data it needs, running it across one machine or several, watching the application while it runs, and keeping a report that outlives the run.
This documentation describes what is in the product today. Where something is planned rather than built, it is marked as such rather than described as though it exists.
Start here#
If you have just been given an account, read Getting started. It goes from signing in to a finished report without assuming anything.
If you are setting JMXPress up for a team, read Accounts and access first, then Distributed agents.
What each part is for#
| Section | What it covers |
|---|---|
| Getting started | Signing in, and a first test end to end |
| Accounts and access | Roles, organisations, access windows |
| Projects and test plans | Keeping a plan with its data and environments |
| Recording a journey | Capturing a journey in a browser |
| Converting what you have | Postman, HAR, cURL, OpenAPI, LoadRunner, NeoLoad |
| Running a test | Load profile, test data, where it runs |
| Distributed agents | Running load from more than one machine |
| Live results | Watching a test while it runs |
| APM integrations | Reading your monitoring alongside a test |
| Reports | What is kept after a run |
| Heap and thread dumps | Collecting diagnostics from a machine |
| Troubleshooting | When something does not work |
| Security practices | Credentials, isolation, what leaves the server |
Where JMXPress runs#
On a server your team controls, against a PostgreSQL database your team controls. Testers reach it in a browser. Recording and distributed load happen on their own machines through an agent that dials out to the server.
There is no public multi-tenant instance to sign up to, and nothing is sent to a third party: the APM credentials you configure stay on your own installation and are used to call your own provider.
Getting help#
Write to support@jmxpress.in. Include the page you were on, what you expected, and what happened instead. There is no ticketing system in between.