Hello, I hope you're all fine. What's your thoughts on:
- Add GraphQL/HTTP Request Sampler https://github.com/apache/jmeter/pull/627 - Add: ElasticSearch backend listener https://github.com/apache/jmeter/pull/615 - Add BackendListener that sends "raw" results to InfluxDB ( https://github.com/apache/jmeter/pull/544) Here are mine: 1) Add GraphQL/HTTP Request Sample: - I am in favor of integrating it to the next release - Testing GraphQL with JMeter looks really painful - The way it is done improves user experience for a technology which is gaining attraction without introducing new dependencies - Providing a plugin might be more complex 2) Add: ElasticSearch backend listener: - The drawbacks I see currently are: - For signing on AWS ElasticSearch, It introduces a dependency on aws-java-sdk and google guava which might not be acceptable. This should be available as a pluggable thing instead - We need to maintain in core a dependency on a 3rd party that has a faster pace in terms of releases - There is already a plugin which is maintained by the PR contributor , this plugin has users. - The addition looks really useful, but I am wondering if it's not better that this one remains as a plugin, as its pace of release can be faster than JMeter one. 3) Add BackendListener that sends "raw" results to InfluxDB In the end and after testing reactivity of the project Vladimir mentioned as a better alternative, I tend to think this should be merged. What the current listener does might not be acceptable in certain contexts. What's your thoughts ? Thanks -- Regards Philippe M.
