Mike Minutillo

Hi @pardahlman. Thanks for the suggestion. We will consider it for a future release.

Particular/NServiceBus#6492 is a related idea

other accounts from other systems could be used as well. This allows the jibbr to say things like: @wolfbyte opened a new issue: (details of issue) Actually since we all...

Thanks for the feedback @lillo42 We will look at improving this in a future release. In the meantime, as this is a non-prod environment, can you [enable installers](https://docs.particular.net/nservicebus/operations/installers) for the...

@lillo42 if you're still trying to figure out which queue is causing the problem we may be able to at least log all operations that are going out. Try adding...

@lillo42 were you able to figure out which queue is causing the issue?

Ah, OK. That makes sense if there was a queue in the message-driven pub-sub subscription storage. We would assume that the subscriber is responsible for that queue, so we don't...

Discussing it again today, we decided that the best approach is to make it configurable.

Had a support case with a customer where they wanted to retrieve the queue name the message came from within the handler. The workaround I provided was to take a...

## Potential solution - Use correlation filters We can keep the topology exactly the same and switch to [correlation filters](https://learn.microsoft.com/en-us/azure/service-bus-messaging/topic-filters#correlation-filters) on the subscriptions. Correlation filters are significantly less CPU intensive...