Service Bus

  1. Open Source Service Bus for Windows Server Like the Service Fabric Team is Doing

    Open Source Service Bus for Windows Server Like the Service Fabric Team is Doing.

    The Service Fabric team is in the process of moving to a Linux version and Open Source. Service Bus for Windows Server is stuck at version 1.1. Keeping with the times and other Microsoft efforts, open sourcing it so it is maintained would be greatly appreciated.
    Service Fabric open source:
    https://blogs.msdn.microsoft.com/azureservicefabric/2017/03/24/service-fabric-net-sdk-goes-open-source/

    9 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 →
  2. Add metric for used space of the partitions of a topic

    In order to avoid QuotaExceededExceptions when sending messages to a topic, it is must be possible to create an alert rule based on the size of the partitions of the topic. Hence there should be a metric for the sizes of the partitions of a topic. It should be possible to define an alert rule that when any of the partitions reaches a certain threshold size (expressed as absolute size in GB or relative size as percentage of full), then an alert can be triggered. In the Azure Portal it should be possible to see the used space of each…

    9 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 →
  3. notify customers of new IP ranges for Service Bus

    It was very difficult to find the list of IP ranges that Azure uses and there is no notification method when new IP ranges are added or old ones removed. This is critical, especially for customers using the Service Bus for secure communication with Azure-hosted applications.

    I discovered that there is a downloadable XML file that is updated on Wednesdays, but I must manually download the file and run a comparison/diff to see if anything has changed. This is very inefficient, especially given that there are probably thousands of customers and administrators who need this information in a more easily…

    8 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 →
  4. Azure Service Bus should support Web Service and REST endpoints for the consumers by default with auditing

    As all enterprise service bus products have, Azure Service Bus should support exposing services with their WSDL and RESTfull endpoints by defaults; without using SDK during consumer implementation. No enterprise can push a 3rd Party for using Azure SB SDK to consume business services... Ans also there should be built-in auditing and montioring features for Azure SB. It should be known that who, when, in waht credentials ..etc connected to the exposed services. Otherwise, each service should save its log to anywhere ..etc

    8 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 →
  5. non partitioned to partitioned entities

    Sending messages from a non partitioned topic means that all subscribers are expected to be non partitioned. To me a scenario where tue service bus could forward unpartitioned entity messages to a partitioned entity

    8 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 →
  6. Please foresee a 'checkbox' to create an ACS namespace in the portal with a new service bus

    Each time we want to create a service bus namespace, we have to use PowerShell, just to add an ACS with the namespace. A checkbox (that is unchecked by default) would be so handy here

    8 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 →
  7. Provide Event Hub viewer / explorer

    It would be good if some sort of viewer/explore was provided for looking at the events within an Event Hub. This could be done either via the portal or Azure Storage Explorer.

    When developing I currently use https://marketplace.visualstudio.com/items?itemName=Summer.azure-event-hub-explorer to view events as they are produced.

    However, it would be good if a tool existed that let you browse events within the retention period. With the possibility to query by timestamp & partition key. As well as the event body, it would be good to be able to see the properties and other metadata.

    We use Event Hub as the integration…

    8 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 →
  8. SUGGESTION: Give minimal throughput statistics on Azure Service Bus Queue and Topics

    I design web-applications for high-scalability, capable of handling a big number of simultaneous users. Typically a single VM can can have 10K, 20K and even u 50K simultaneous uses. In order for me to make proper design decisions with Azure web-applications, I need minimal statistics about some of its vital services.

    I would suggest that Azure give some statistics about its Azure Service Bus service Queue and Topics.

    1) Average number of write message operations per second.
    2) Average number of read-message operations per second.

    It might also be good to vary the size of messages to see how that…

    8 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 →
  9. Increase limit of SAS keys per namespace

    Currently the number of SAS keys is limited to 12. We have many users who post messages to a single queue and would like to give every user a separate SAS key.

    7 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 →
  10. Rename NuGet package ServiceBus.v1_1

    Rename NuGet package ServiceBus.v1_1 to WindowsServer.ServiceBus or similar. Using underscore in package name is not recommended by the NuGet naming conventions.

    From NuGet naming conventions:
    "Package IDs should follow a pattern similar to namespaces in .NET. For example, Ninject.Mvc3 instead of Ninject-Mvc3."

    It would also make it look nicer and similar to WindowsAzure.ServiceBus package.

    Another issue is that when used in combination with Asp Net Core it gives an error when trying to publish the solution:

    "Error: The package ID 'ServiceBus.v1_1' contains invalid characters. Examples of valid package IDs include 'MyPackage' and 'MyPackage.Sample'"

    7 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 →
  11. monitor subscriptions

    My customer would like to be able to monitor subscription metrics through azure monitor. Currently there is no way to see if a subscription is successfully processing messages. A user can monitor topics to see that it has sent outgoing messages to subscriptions but not monitor the subscription to see that it is functioning and provide alerts to notify users of that inactivity.

    7 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 →
  12. service bus namesapce scale configuration

    When adding throughput unit to event hubs in the scale tab, the 'yes' button does nothing in IE or Chrome.

    7 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 →
  13. unambiguous date format

    so the date format here https://azure.microsoft.com/en-us/documentation/articles/service-bus-build-reliable-and-elastic-cloud-apps/ is 05/10/2016 which for most of the world is ambiguous

    I suggest yyyy-mm-dd

    6 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 →
  14. Keep getting internal server error on push messages to iOS

    We are sending push messages to iOS and keep getting error messages.

    Please see attached screen.

    The Push Notification System returned an Internal Server Error

    6 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. Hippa compliance for DocumentDB

    Currently this is stopping us from developing on the DocDB service.

    6 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 →
  16. Detailed information about active listeners

    This has been suggested before -
    In comment here:
    https://feedback.azure.com/forums/216926-service-bus/suggestions/3695944-service-bus-relay-monitoring
    and here
    https://stackoverflow.com/questions/26118433/identify-a-azure-relay-servicebus-listener.

    It would be great to be able to identify active listeners on a particular relay. I've also heard this can be a issue in the WCF relay.

    I had a active listener in the portal (and eating all messages, with timeout), but not running my software anywhere. It would have been nice to see any insight to where it was running, f.x. IP address or machine name.

    6 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 →
  17. Event Grid events raised for Sessions

    Service Bus can be configured to raise events when: "This event is generated if you have active messages in a queue or a subscription and there are no receivers listening."

    For session based queues it would be more useful if it did this per session. This would allow multiple sessions to be processed simultaneously.

    The SessionId should be added to the event payload so that the receiver knows which session to read.

    6 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. Event Grid events available in Standard SKU

    Currently a Service Bus can only be configured to raise events if it is Premium, Standard and Basic are not supported. This makes this feature prohibitively expensive for most.

    6 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 →
  19. Service Bus Geo-feature is way expensive

    Service Bus Geo feature is a cool feature, which is requiring premium tier license, when using price calculator to work out the cost difference between standard tier and premium tier, it seems our cost will jump from AUD $16.45 per month to $1850 ($929.62 x 2). this is a huge jump. can you please confirm if this is correct?

    5 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 →
  20. Make message rollback (abandon) transactable

    Currently, if wrapped in a TransactionScope, calls to BrokeredMessage.Abandon are basically ignored, i.e. they have no effect, and the message cannot be received again until the message lease timeout has expired. It's not that it's "not transactable" in the sense that some of the messages are abandoned (rolled back) at the end of the TransactionScope and some are not...it's "not transactable in the sense that if the message is enrolled in a TransactionScope, the call to Abandon simply does not ever abandon any messages.

    The ability to either commit or rollback an entire batch of messages seems critical to a…

    5 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 →
  • Don't see your idea?

Service Bus

Categories

Feedback and Knowledge Base