Yuri Bushnev

That's simple. For personal needs, I added a few more plugins after that.
For example, you can see that one of the steps mentioned above has the "matrix" plugin which is not listed in the original file.
As it doesn't change the workflow and described solution, most probably I just didn't redo the screenshot after that.

Hi Firm.
Could you please attach some logs? This issue explanation is quite wide and there are many different reasons which might be the root of the cause (just an example, https://github.com/kubernetes/minikube/issues/2298)

Hi Vincent. Thanks for your comment. However, this topic is mainly about monitoring and not results storage. Regarding results storage, I believe that it is always better to store that into some time series metrics db which provides an ability to have customizable monitors and easy way of baselines comparison.

Hi Leo.

That's easy. If you use "org.apache.jmeter.visualizers.backend.influxdb.InfluxdbBackendListenerClient" backend listener implementation, then you can specify the influxdb url in this format: http://localhost:8086/write?db=performance&u=myusername&p=mypassword

And if you use "rocks.nt.apm.jmeter.JMeterInfluxDBBackendListenerClient" listener implementation then you should have influxDbUser and influxDbPassword fields right away in the fields box.

Let me please know if you still have some troubles with this answer.

Thanks, Mohit. You can find more articles on bushnevyuri.com or https://www.blazemeter.com/blogs-on-author/937

Thanks! If you have any question regarding JMeter usage in mind (which is not clear and you can not find answers in google for that), please let me know and I will try to think how I can reveal that in such kind of article =)
You can find more articles on bushnevyuri.com or https://www.blazemeter.com/blogs-on-author/937

Thank you for feedback! =) You can find more articles on bushnevyuri.com or https://www.blazemeter.com/blogs-on-author/937