Add an example dashboard which shows the reported metrics and describe the usage in the README

Deleting any parameter in the backend listener, not actually deleting it.

Steps to reproduce:

1. Add a backend listener and select com.dynatrace.jmeter.plugins.MintBackendListener
2. Delete any parameter(s)
3. Click on any other element in the test plan
4. Click on the backend listener again, you could see the deleted parameters are added again.

I did a simple load test against my local app. I have found conflicts between the dynatrace metrics and JMeter metrics.

JMeter Summary Report

Conflicting Metrics:

I've implemented the plugin on my companies jmeter tests and everything seems to report properly during the test. 1 thing that I can't figure out is we consistently get a 400 error when the listener is starting up and configuring itself for the first time.

In the Jmeter logs we get a WARN(ing) on the first time it submits:

Does this matter? Seems like a startup order issue. There are not metrics to send at that time.

I've tried altering my payload and making small changes but no luck. Otherwise it works well and sends in the metrics for the rest of the test.

When we add the plugin as a maven dependency, it breaks our code (which needs JMeter dependencies like ApacheJmeter_Core:

    <dependency>
      <groupId>org.apache.jmeter</groupId>
      <artifactId>ApacheJMeter_http</artifactId>
      <scope>provided</scope>
    </dependency>
<!-- Breaks the module compilation when added -->
    <dependency>
      <groupId>com.datadoghq</groupId>
      <artifactId>jmeter-datadog-backend-listener</artifactId>
      <scope>runtime</scope>
    </dependency>

Datadog works fine as the plugin dependencies are correctly scoped as provided:
https://github.com/DataDog/jmeter-datadog-backend-listener

As of now, we're forced to add ApacheJmeter_Core as provided dependency to our pom.xml as a workaround to fix this issue:

    <dependency>
      <groupId>com.dynatrace.jmeter.plugins</groupId>
      <artifactId>jmeter-dynatrace-plugin</artifactId>
      <scope>runtime</scope>
    </dependency>
    <!-- Required due to dynatrace plugin "runtime" dependencies -->
    <dependency>
      <groupId>org.apache.jmeter</groupId>
      <artifactId>ApacheJMeter_core</artifactId>
      <version>${jmeter.version}</version>
      <scope>provided</scope>
    </dependency>

Please change the scope to provided instead of runtime to avoid breaking the compilation classpath of modules which need your plugin.

Would it be possible to get this library to published into maven repo ?. so it will be integrated the maven and Jmeter

I would like to introduce a new parameter called "enable". The default can be true - but - I would like to use this parameter to enable/disable this extension via a JMeter parameter instead of having to enable/disable it through a JMX setting.

My use case is that we leverage JMeter with the open source project keptn (www.keptn.sh). When uploading a JMX File that contains that Dynatrace plugin I would like to enable/disable this extension via a parameter that Keptn passes to JMeter. This gives us more flexibility to control the behavior instead of having to upload different versions of the same JMX file

I was getting many errors like this:
2021-01-16 00:07:24,990 INFO c.d.j.p.MintBackendListener: Start MINT metric sender for url https://zzzz.live.dynatrace.com/api/v2/metrics/ingest failed with General Error executing connection check for MINT server, setting enabled state to false

I tracked it down to a lastRequest.get() call in MintMetricSender.checkConnection() that has a timeout of only 1 second. By changing the timeout to 30 seconds, I am able to avoid the errors.

Also, unless I set loglevel to DEBUG, it doesn't tell me that it is a timeout.

The exception-catching code looks like this

		catch (ExecutionException | TimeoutException | InterruptedException ex) {
			log.debug("Error executing connection check for MINT server", ex);
			throw new MintConnectionException("General Error executing connection check for MINT server");
		}

I would suggest you log.warn, or log.error, the exception type, And of course, make the timeout longer.

Thanks for your efforts!

Is your feature request related to a problem? Please describe.
Since we use protocol based testing with JMeter we have a lot of resources as test steps in our test plan. But only a few a necessary to report to Dynatrace.

Describe the solution you'd like
We would like to have the possibility to filter sampler names by regex as the InfluxDBListener does.

As currently i could see there is only one service we can specify in backend listener to send the transaction dimensional metrics to respective service.
If we have jmeter test plan with multiple services then how exactly we can send the transactional mint metrics to respective services in dynatrace. Is there any automatic way to achieve this?

Which allows for easier management of jmeter plugins / automation (installing the plugin through command line using PluginsManager).

When passing in a wrong or invalid API Token or Dynatrace API Endpoint the plugin tries to call that invalid combination everytime it tries to send data. This results in a lot of error log outputs during a JMeter test execution that uses this plugin

I suggest that the plugin should do an initial check on whether the API is reachable using the passed Token. If that is not the case the plugin should create a single error log but then stop sending data as this data would never reach Dynatrace anyway

From the graph we can see the metric captured are in K and they are not in seconds. Also these values are not matching with Jmeter html report.

Is this something can be looked into this issue.

When I try to send Requests to our Dynatrace instance, the Backendlistener fails to send them. I added "setProxy()" to the creation of the httpClient in the MintMetricSender Class. After doing that, sending the requests worked.

The listener currently doesn't expose the P90 and P95th Percentile metrics.
I would like to request new feature to also include the P90 and P95 percentile metrics for this listener.

Thanks