GraphiteBackendListenerClient on Jmeter is sending wrong TPS count value
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.3k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
### Expected behavior
GraphiteBackendListenerClient configured on Jmeter 5.5 and 3.3 should send correct throughput value (TPS) to influxDB.
### Actual behavior
GraphiteBackendListenerClient configured on Jmeter 5.5 and 3.3 is not sending correct throughput value (TPS) to influxDB using master-slave (distribute testing) functionality: whenever the generated traffic volume is less then 100 TPS, the value that Backend listener plugin sends to InfluxDB is equal to 100 (as a default threshold is defined somewhere).
Attached the screen which shows on left side Grafana dashboard showing the TPS count, on the right side the jmeter-server.log which shows the TPS generated by the slave.
### Steps to reproduce the problem
I used throughput shaping timer plugin to define target TPS to be reached by the slave. I used 1 thread only. I launched Jmeter in distribute testing mode (master-slave). I configured the backend listener plugin to send the metrics to influxDB and Grafana to catch the values from InfluxDB
### JMeter Version
3.3 and 5.5
### Java Version
_No response_
### OS Version
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.