Your machines
JMXPress runs on a server you control. Recordings, results, reports and APM credentials stay on that installation.
About
JMXPress
Everything around the JMeter run
What it is
JMXPress is a performance engineering workbench. It covers what happens around a JMeter run: capturing a journey, turning it into a 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.
Why it exists
The work around a load test is usually spread across a recorder, a spreadsheet of test data, somebody’s laptop, a monitoring tab nobody saved, and a results file emailed afterwards. JMXPress keeps them in one place and attaches them to the run they belong to.
How it is built
It is a Flask application over PostgreSQL, with row-level security enforcing the separation between organisations, and an agent that dials out from a tester’s machine rather than listening for a connection. It is run on a server the team controls.
Who builds it
Developed by JMXPress Team.
Questions, problems and requests go to support@jmxpress.in. There is no ticketing system in between.
Separated by the database
Every tenant-owned table carries an organisation and a row-level security policy, so the separation between teams is enforced by PostgreSQL rather than by remembering a WHERE clause.
The agent dials out
A tester’s machine makes outbound calls to the server. There is no listening socket on anybody’s laptop and no port to open.