Service Bus

  1. Autoscale based on topic-subscription length

    Instead of autoscaling on queue length, i would like to be able to scale on topic-subscription length

    347 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Provide gracefull shutdown feature to Message Pump in Queue and Subscription Clients

    There is not a good way to deal with a graceful shutdown of a Worker role using the OnMessage approach of processing queue messages off the service bus. It would be nice if you could call StopProcessing, or something similar on the QueueClient or SubscriptionClient so that they would stop their internal receive loop, but finish processing the messages they may already be processing. A count property of active processing messages would also be helpful so that in an OnStop method on the worker role you could call the StopProcessing and enter a loop till the active processing messages was…

    325 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  16 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Queue purge

    Provide an API for purging of a queue, without having to delete and recreate the queue.

    209 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Using a filter with EventHub data

    Will we be able to use a filter in the future for the EventHub data? I'm designing a new solution for a customer and it looks like EventHubs are great for sending and receiving our near-realtime data. Downside is when receiving the data, we receive all data of all our devices in the world. Most of the time, our clients only want to see data of one (or a few) device. We could of course filter the data by ourselves, client side, but this would cost a lot of bandwith.

    108 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Detect Duplicate messages in the service bus queue (not time based but content based)

    The current duplicate detection Azure service bus works based on the time frame but not based on the actual content of the queue. It would be great if we could have duplicate detection based on the current content of the Queue.
    E.g.
    If there is a message with a message-id 'XYZ' and then we try to add a new message with message id 'XYZ', then it should not be added.

    Alternatively, at least providing a possibility to check whether message-id exists in the queue would also be great.

    102 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Change the Service Bus SDK to be a Portable Class Library

    Right now, the Service Bus SDK requires the Full .NET Framework. For Xamarin and .NET Core situations, it would be much better if the Service Bus SDK were released as a Portable Class Library. (Oh, and open-sourcing the SDK would be great, too.)

    99 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add gzip support for sending/receiving multiple events from/to event hub.

    Today, the event hub rest api does not support gzip out of the box, this is very important feature especially when dealing with a lot of events from mobile client for example.

    97 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Enable indefinite storage of events on Event Hub to allow for an Event Sourcing architecture.

    When building an application using Event Sourcing, the events are the true source of all data. Replaying events and creating different projections at any time during the lifetime of the app is crucial. Currently Event Hubs only supports up to a 7 day storage policy. This means that it cannot be used with Event Sourcing. An example of this kind product is Greg Young's EventStore. https://geteventstore.com/

    94 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Service Bus Metrics to Operations Management Suite (OMS)

    Please now that there's a rich API capability for queue metrics, let's support pushing the metrics to OMS for monitoring.
    And make a servicebus OMS Solution?

    75 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add metric for the number of deadletter messages in a Service Bus Queue

    This would allow users to create alerts in Azure Monitor for dead-lettered messages.

    70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support propagating content-type and content-encoding headers as user properties for event hub REST API.

    I would like to request that MSFT consider providing access to these properties so that we can use the same standard properties across both HTTP and AMQP. Currently, when using HTTP to send to event hub if you specificy a Content-Type or Content-Encoding those headers are not included with the user properties as previously stated. When using AMQP to send to event hub (and the EventData class) you can explicitly add Content-Type and Content-Encoding properties as user properties, and that works fine such that they are received as user properties.

    The problem with this is that it creates the requirement…

    65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. BrokeredMessage.Defer(); should send a message to the back of the line

    I use the Azure Service Bus in a geographically distributed environment. I also process messages in vertically and horizontally scaled out services.

    Very often I will receive a message from the service bus for processing, but don't have enough information to complete the processing, (most of the time this is because I am waiting for SQL replication across continents) so I'll have to try again later.

    Seems like a job for BrokeredMessage.Defer()! But alas, that causes the message to immediately get returned when I call Client.Receive(); even if there are thousands of messages in the queue / subscription that I…

    65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add "Messaging Quotas" and current usage metrics of each to performance dashboards.

    We would like to see a presentation of the Message Bus "Messaging Quotas" and current usage of each quota in Message Bus performance dashboard or make them accessible via the API.

    For example:
    NetMessaging: 1,000
    AMQP: 5,000

    There are a range of performance quotas documented here:
    https://azure.microsoft.com/en-us/documentation/articles/service-bus-quotas/

    I would like to understand our metric use under each of these quotas and ideally alert on a threshold.

    63 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. 63 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Implement queue priority pattern

    Implement priority queue pattern, to use one queue or topic subscription that can reorder its messages according to theirs priority.

    Pattern description https://msdn.microsoft.com/en-us/library/dn589794.aspx

    60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Increase the maximum message size for Premium

    Premium is currently limited to a maximum message size of 1 MB. It would be great if you increased the maximum message size for Premium to 10 MB.

    I see that there was a more general request regarding this that has been closed, https://feedback.azure.com/forums/216926-service-bus/suggestions/3933438-increase-the-256k-maximum-message-size-limit-of-br, but I assume that was before Premium was thought of.

    55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add metrics for the number of concurrent connections

    It is better to provide the metrics or REST API to get the number of concurrent connections, because our connections are throttled if exceeding the defined quota.

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Hybrid connection client service

    There is a tool (https://www.microsoft.com/en-us/download/details.aspx?id=44216) for the "old" BizTalk hybrid connection that let vm or web/worker role to use hybrid connection. Because of the "dead" of BizTalk hybrid connection and the "rise" of sb relay hybrid connection, it would be appreciated to have its own client service tool.

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Event Grid integration with Service Bus Standard Edition

    It would be good if Event Grid is integrated with Service Bus Standard Edition . As of now Event grid can listen to only premium tier service bus events. By supporting Standard edition of Service bus ,it will increase event driven messaging adoption .

    50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Our eventual goal is to connect every service in Azure to publish events, however, we haven’t started on Service Bus Standard integration yet.

    We’re passing your feedback along to the Service Bus team, but as always make sure you let them know as well so they hear your voice!

  20. In a paired namespace scenario, make the primary namespace do the syphoning in a disaster recovery situation.

    Currently, in the paired namespace scenario detailed in https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-paired-namespaces, "at least one of the clients" needs to run the syphon.

    I don't think it's necessary to have that on the client side. This creates all sorts of requirements on the client side, such as availability.

    It's probably much more convenient if a primary queue/topic knows about its secondary queue and starts syphoning on its own as soon as it goes online again.

    49 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 9 10
  • Don't see your idea?

Service Bus

Categories

Feedback and Knowledge Base