> "In distributed testing, JMeter now automatically prefixes thread names with > engine host and port, this makes the counting of threads correct in the HTML > report without any other configuration as it was required before "
Not entirely sure if I'm understanding correctly or know enough of JMeter yet, So, change the current ThreadNames from, ex: - Thread Group XYZ 2-13 To something like?: - ServerABC:1234 Thread Group XYZ 2-13 I'm writing a " BackendListenerClient" plugin to collect and ship the data to InfluxDB (the existing one is not satisfactory) and I'm having to breakdown the Thread «Real» Name & Thread Number from inside the reported "SampleResult result.getThreadName()". (isolating the Thread Group ID is mandatory in order to be able aggregate results per Thread Group, of course) I'm concerned that if the server identification is also added to the mix, that it might become impossible to deterministically separate the Server ID from the Thread Group ID... I was going to ask how that is prefixed, wondering whether it will be prefixed in a deterministic way so that we can breakdown ThreadName into its separate components. But a better question might be - why is it prefixed into the existing field "ThreadName" instead of offered as a new separate value (like URL or ResponseMessage are different "columns")? If Server ID really needs to be bundled into the Thread ID & Thread Number in the field ThreadName (which are already bundled together for possibly a similar reason), where can I find info on how that is prefixed, how will we be able to reliably separate the Server ID from the Thread ID? <- I'd like to code that into the plugin now in advance, so that I won't need to make any code changes for the upcoming new version. Regards, Paulo Augusto Maia Borges -----Original Message----- From: Milamber <[email protected]> Sent: 09 September 2018 18:35 To: JMeter Dev List <[email protected]> Subject: [VOTE] Release JMeter 5.0 RC1 Hello, The first release candidate for JMeter 5.0 (r1840419) has been prepared, and your votes are solicited. This release brings a lot of new features and improvements, and also fixes bugs. Please, test this release candidate (with load tests and/or functional tests) using Java 8 or 9 on Linux/Windows/Mac OS, especially on the changes. Feedback is very welcome within the next 72 hours. You can read the New and Noteworthy section with some screenshots to illustrate improvements and full list of changes at: http://home.apache.org/~milamber/jmeter-5.0RC1/docs/changes.html JMeter is a Java desktop application designed to load test functional behavior and measure performance. The current version targets Java 8 / 9. Download - Archives/hashes/sigs: https://dist.apache.org/repos/dist/dev/jmeter/v5.0_RC1/ (dist revision r29231) RAT report: http://home.apache.org/~milamber/jmeter-5.0RC1/dist/rat-report-jmeter-5.0RC1.txt SHA512 hashes of archives for this vote: see footnote [1] Site Docs are here: http://home.apache.org/~milamber/jmeter-5.0RC1/docs/ Maven staging repository is accessible here: https://repository.apache.org/content/repositories/orgapachejmeter-1030/org/apache/jmeter/ Tag: https://svn.apache.org/repos/asf/jmeter/tags/v5_0_RC1/ Keys are here: https://www.apache.org/dist/jmeter/KEYS N.B. To download the dependencies: "ant download_jars" To create the jars and test JMeter: "ant package test". JMeter 5.0 requires Java 8 or later to run. Some known issues and incompatible changes are listed on changes page. http://home.apache.org/~milamber/jmeter-5.0RC1/docs/changes.html#Known%20problems%20and%20workarounds All feedback and vote are welcome. [ ] +1 I support this release [ ] +0 I am OK with this release [ ] -0 OK, but.... [ ] -1 I do not support this release (please indicate why) The vote will remain open for at least 72 hours. The PMC members please indicate the mention "(binding)" with your vote. Note: If the vote passes, the intention is to release the archive files and rename the RC tag as the release tag. Thanks in advance! Milamber === [1] SHA512 hashes of archives for this vote: 0756d3374a8431e85153071fcc4e443d1072e489f87323968a8b32c0cb731facb1ce0a6c7909e0ffbd034a33621e6b44ac209a38a20212015995580b267774b2 *apache-jmeter-5.0.tgz 335a8ba97727ec118c9864ff999a02f55576a11f74e8cec648157eb3e5a25ad9fc8c60d0154630041b227f3ed93a2efca968491f664f56bcd221f1faa894485f *apache-jmeter-5.0_src.tgz cb294aaf43fafb585d61bf2d8db299c53d7b25e12db277ca4436537ac28f7d4aa27a50bfd3114fb2b446c3ba2059eeae9a29fddddb1f915efef509a6b83ce620 *apache-jmeter-5.0_src.zip 5fd9b7aa1a4a9c6ae8b981383ba7f0f15ba031b65df3c85735891cdd0ff72f958514d30432cf3d37aa3c4ddbc9a41cf60371895c0caeaab0ca0b51538f24a055 *apache-jmeter-5.0.zip The information in this e-mail and any attachments is confidential and may be legally privileged. It is intended solely for the addressee or addressees. Any use or disclosure of the contents of this e-mail/attachments by a not intended recipient is unauthorized and may be unlawful. If you have received this e-mail in error please notify the sender. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of TEMENOS. We recommend that you check this e-mail and any attachments against viruses. TEMENOS accepts no liability for any damage caused by any malicious code or virus transmitted by this e-mail.
