3dgiordano commented on issue #5136:
URL: https://github.com/apache/jmeter/issues/5136#issuecomment-1554618436

   Hello @AllardQuek 
   
   This issue is migrated from Bugzilla.
   The @asfimport user is a user that was used for the migration.
   
   Originally what Michael Johnson pointed out in Bugzilla is that BlazeMeter 
has a plugin.
   However, the plugin of that time (2022) is a Correlation plugin where the 
rules must be previously specified (at that time not really related to the 
automatic method indicated by the person who initiated the order)
   
   It is possible that at that time the BlazeMeter CR plugin had not yet 
resolved its support for JMeter 5.5.
   But versions after that date fixed it.
   The lates version supports the entire JMeter 5.x family
   
   In addition, in its 2.x version of the Correlation Recorder plugin, bring 
the initial support for Auto Correlation.
   That was released a month ago.
   
   Autocorrelation is an automatic mechanism that detects potential elements to 
be correlated and automatically creates correlation rules.
   That feature is what Takashi Imoto initially mentioned back in 2019, but 
with a different approach taken by the team of BlazeMeter.
   They improved their Correlation Recorder to also have an automatic 
correlation method.
   
   You can find the information in their GitHub repository where you have 
access to the documentation
   https://github.com/Blazemeter/CorrelationRecorder
   
   There is also a recorded webinar on the release of version 2.x
   https://www.blazemeter.com/webinars/ignite-auto-correlation
   
   These topics related to autocorrelation implemented in Correlation Recorder 
are not related to this request to support Autocorrelation in JMeter.
   If you have questions or problems with BlazeMeter Correlation Recorder, you 
can ask for help in the issues section in BlazeMeter's Correlation Recorder 
repository. 
   https://github.com/Blazemeter/CorrelationRecorder/issues
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to