Hi @nram , thank you for making it easier but this is the outcome:
I published the messages at the rate and size you mentioned while my consumer was running on the other console.
I observed that the messages were still being consumed at a very slow rate BUT that does not still qualifies to flag it as a “slow subscriber” in our Grafana Panel which has the query using the function “solace_client_slow_subscriber” . Also noticed when I run the following it consumes but intermittently and really slowly.
$ ./sdkperf_java.sh -cip tcps://myvpn.messaging.solace.cloud:52444 -cu test-user@myvpn -cp ‘password’ -sql test-queue -sd 10000 -sdc -1 -cor
Can you please suggest how can we stress the consumer (maybe more) to raise a flag “slow subscriber” for the client ?