ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Blazemeter Request Stats report shows different results from data in Database and APM reports


Article ID: 221229


Updated On:




When adding up the number of requests for a set of element labels which correspond to the submission of an order on the Request Stats report of a BlazeMeter test the total does not match the number of new entries added to the database.  The total of requests is much lower than the number of new entries in the database.  The APM reports reflect the number of new entries added to the database.

The Request Stats report is also missing element labels for all of the requests that were made when the JMX script was executed.


The JMX script contained more than 100 element labels which resulted in the creation of the AGGREGATED LABELS row on the Request Stats report.  Some of the element labels that correspond to the submission of an order were rolled up into the AGGREGATED LABELS row making it impossible to determine the actual number of submit requests made by the test from this report.  The missing labels in this report were also rolled up in the AGGREDATED LABELS row.  This is per design as documented in the Aggregated Labels section of the Request Stats Report article.


Release : SAAS



The best way to assure that all critical element labels are reported on the Request Stats report page is to reduce the number of element labels that the test generates.

One means of doing this is to add JMeter Transaction Controllers to organize different segments of the test and control how they appear in BlazeMeter reports.

The What is JMeter's Transaction Controller? blog has some useful information for using this element in a JMeter test.