search cancel

Missing transactions on the Request Stats report page of a BlazeMeter Performance test


Article ID: 214496


Updated On:




The Request Stats report page of a BlazeMeter Performance test does not show all of the transaction labels generated by the test script executed.  One of the transaction labels found on this report is AGGREGATED LABELS.


Release : SAAS



This is by design as documented in the Aggregated Labels section of the Request Stats Report article.


The Request Stats Report only displays the first 100 element labels executed by a test.  If the test script has more than 100 labels, the following will apply:

  • The first 100 labels executed will be displayed normally.
  • The AGGREGATED LABELS row will appear and will only report the sample count for those labels beyond the first 100 displayed.
  • The ALL label will still track all 100+ labels and account for them in its calculations.
  • Though the Request Stats Report can be filtered by scenario and location, it will nonetheless still not display more than 100 labels.
  • A multi test may contain up to 300 labels before aggregating them, but the underlying scenarios that make up the multi test are still limited to 100 unique labels each. So if the need exists to show more than 100 labels, a workaround may be to split the JMX up into multiple pieces, each containing less than 100 unique labels and combine them in a multi test.
  • Multi tests with over 300 labels do not show an AGGREGATED LABELS row.