Eldert Grootenboer
Eldert Grootenboer
Thank you for suggesting this feature. We have opened an investigation task for this in our backlog, and will update this issue when we have more information.
We have opened an investigation task for this in our backlog, and will update this issue when we have more information.
We have opened an investigation task for this in our backlog, and will update this issue when we have more information.
Hi, this has surfaced to the top of our backlog, and we hope to implement this in the coming months.
We have added this to our backlog, and will update this issue when we have more information.
We had some internal discussion about this, but looking at the remarks section we think this is already addressed? _If a message is sent via a transfer queue in the...
We have opened an investigation task for this in our backlog to check the possibilities of exposing this, and will update this issue when we have more information.
We have opened a task for extending metrics to subscription level in our backlog, and will update this issue when we have more information.
In our benchmarks we normally see numbers of around 4MB/s per MU, as described [here](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-performance-improvements?tabs=net-standard-sdk-2#benchmarks). However, it will depend a lot on which features you are using. There is not...
@lucasmaj Correct, although it will depend on your specifics, such as message size, features used, etc. That is why we recommend using the benchmark tool with your own production-like workloads....