AddNewPlugin_JMXAuditor - Initial Release#831
Merged
undera merged 1 commit intoundera:masterfrom Apr 25, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
I'd like to submit a new plugin — JMXAuditor — for inclusion in the repository.
I built this because the same classic mistakes keep slipping through to the load run. You leave a GUI listener on the load path, spin up the environment, generate the data, run for half an hour — and the throughput numbers are off. Or someone leaves a plaintext password in a request body and only spots it after it's already in the logs.
Existing approaches answer "is this test plan valid?" — does it parse, does it execute. JMXAuditor answers a different question: "is it well-designed?" A plan can be perfectly valid and still leak credentials in the request body, drop throughput from a GUI listener on the load path, or send identical requests with no think time. Those issues only surface at run time, when the cost of fixing them is highest. JMXAuditor scans the open test plan and flags those issues in seconds.
What it does:
Plugin is on Maven Central (io.github.sagaraggarwal86:jmxauditor-jmeter-plugin:0.6.0), Apache 2.0 licensed, and targets JMeter 5.6.3 / Java 17.
Happy to answer any questions or make adjustments to the entry.
[Sample_Report.html](https://github.com/sagaraggarwal86/JMXAuditor-jmeter-plugin/blob/main/docs/Sample_Report.html)