Replies: 3 comments 3 replies
-
Hi @shaqb , yes, this should be possible as well. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi @ludeknovy long time no speak! I was wondering if you ever got a chance to implement this feature? |
Beta Was this translation helpful? Give feedback.
2 replies
-
Nice! Thanks dude!
…On Fri, 27 Oct 2023 at 12:11, Ludek Novy ***@***.***> wrote:
Ahh, actually it looks like I’ve finished it, see #221
<#221>
—
Reply to this email directly, view it on GitHub
<#220 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEWBYKKCI26634UML5P735DYBOJHTAVCNFSM6AAAAAAZ5WL2GSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TIMBSGYZTO>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey @ludeknovy - another one from me if possible!
We had a situation in our load test where we had threads dropping out. We can see that in the graph here:
However we have many thread groups in our scenario and it's hard to see which thread group was dropping. When we use the Jmeter report we can filter by thread group like this:
, and it's clear which one has the issue.
Would it be possible to have something similar? We would then be able to determine which thread group had the issue and target that one accordingly.
Beta Was this translation helpful? Give feedback.
All reactions