Save filters per Connection

[trekco]

Can you please add the ability to save a filter per connection.

Currently when you save a filter it gets applied to all connections.

thank you

[bertenvdb]

This is the only feature I'm currently missing.

[ErikMogensen]

I think the best way forward would be that you select which type of service (Event Hubs, Service Bus, Notification Hubs or Relay) a connection string belongs to. Then it only opens that service. That would make loading namespaces using the latest SDKs a lot cleaner. Otherwise they would behave badly (exceptions and timeouts) when trying to load a namespace belonging to another service.

However, there are two issues with this:

• If you have a mixed namespace you'll only be able to see entities from one kind of service at a time. However as described in this blog post from 2016 it hasn't (in general) been possible to create such namespaces for the last eight years. I also know that the Azure Messaging Product Group is actively trying to migrate the existing ones to dedicated namespaces. We do have to support the ability to have a connection string used by multiple services as separate connections, just not opened at the same time.
• Today you can filter to only see Queues or Topics. That won't be possible anymore. If you have a huge number of one of these entities you may run into delays when loading, but that is an edge case.

What do you think?

[SeanFeldman]

I think the best way forward would be that you select which type of service (Event Hubs, Service Bus, Notification Hubs or Relay) a connection string belongs to.

I've been a big proponent of breaking SBE into apps per service. The unified model worked well when there was a single SDK. But now these are separate SDKs; they are developed and progressed independently, with very different features. The approach taken with EventGrid lately is a great example. So, splitting connection strings based on the service type is the right approach 👍