Bug 64562 - InfluxDB results does not match with Jmeter result due to aggregation
Summary: InfluxDB results does not match with Jmeter result due to aggregation
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.3
Hardware: All All
: P2 enhancement (vote)
Target Milestone: JMETER_5.4
Assignee: JMeter issues mailing list
Keywords: PatchAvailable
Depends on:
Reported: 2020-06-26 19:00 UTC by Jyoti Prakash
Modified: 2020-07-01 08:38 UTC (History)
0 users

Example screenshot (105.80 KB, image/jpeg)
2020-06-26 19:00 UTC, Jyoti Prakash

Note You need to log in before you can comment on or make changes to this bug.
Description Jyoti Prakash 2020-06-26 19:00:11 UTC
Created attachment 37335 [details]
Example screenshot

JMeter, by default adds the sampler metrics for a common sampler in the span of influxDB interval duration and send aggregated values to Influx DB after given interval.

Jmeter calculates the transaction metrics (Min, Average, Maximum, 90% Line, etc) from raw results where all transaction metrics are stored vs while sending into InfluxDB from Jmeter, It aggregates metrics according to time interval instead of sending raw results.

This causes the discrepancies between Influx DB metrics and Jmeter Metrics.

If we can modify code to send all result samples rather that aggregation then it will resolve mismatch issue.
Also, we can just send response time and need not to send min, max, and percentile because for 1 result row, time will be same for all computation, however for Summary we may need that.
Comment 1 Graham Russell 2020-06-26 20:15:03 UTC
This is why I created and use https://github.com/apache/jmeter/pull/544
Comment 2 The ASF infrastructure team 2022-09-24 20:38:20 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5350