Storage

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Queues - Add Multiple Messages in a Single Transaction

    “Enhance the Queue API” (http://feedback.windowsazure.com/forums/217298-storage/suggestions/1574639-enhance-the-queue-api) had two features. One was to be able to update the invisibility timeout of a message, which is now completed. The other was to be able to add multiple messages in a single request. If you want that feature, please vote here.

    221 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  2. Infinite TTL for Queue Messages

    Currently messages in your Queue are discarded after 7 days. I'd like to have the option of messages living in my Queue until I get around to processing them no matter what..

    147 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  11 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add queue length monitoring and alerting

    It would be really helpful to be able to monitor the queue size and set alert rules when it exceeds certain threshold.

    119 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  4. Batch Insert of queue messages

    Hi there,

    It would be great if I could do batch insert (add) of messages. Often times I need to add several hundred or thousands or messages to a queue, and today I have to add them one by one. This is also related to the small size limitation of each message.

    119 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add metadata support to storage queue messages

    Please add the capability to add custom metadata to storage queue messages so that we can more easily implement additional communication features on top of them (correlation, header based routing, ...)

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  6. Queues: ApproximateMessageCount: Return numbers for both visible and invisible messages

    We would like to be able to see both the number of invisible messages and the number of visible messages (today we get the total).

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  7. Invalidate pop receipt when message becomes visible

    Currently, there's a gap between a single and multiple consumers scenarios. When a pop receipt is issued and visibility timeout expires, message becomes visible _and_ still can be delete with the original pop receipt. That is not the case when multiple consumers are participating. Original pop receipt becomes invalid once visibility timeout expires and another consumer gets the message.
    The behaviour should be consistent for one or many consumers (just like ASB does it) and pop receipt should not be accepted once expired (message becomes visible).
    More details on this issue are available at this GH issue raised with Azure…

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  8. Increase the maximum message size of 64k. I know, Sb queues support 256k, but they are too darn slow. We don't need all of the features of

    Please increase the max message size limit of 64k. I know SB queues support 256k, but we don't need all the extra features and they are way too slow for our needs. We are in fact moving from SB queues to Storage queue now because of perf issues, and the only thing nipping at us is the reduced message size. 256k would be perfect and would make for a nice parity between the queue.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  9. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow adding custom headers to Azure Queue messages to support tracking of distributed business transactions

    AppDynamics, our Application Performance Monitoring software, needs to be able to add headers to Azure Queue messages, so we can track them as they are picked up and processed by worker roles. This will allow Azure users to see the full, profiled view of their business transactions as they go from role to queue and then to other roles that process them. Such insight into application performance can be invaluable for monitoring and debugging complex Azure deployments.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  11. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  12. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow Storage Queue Get Messages to specify MessageId via URI Parameter

    The caller could have previously gotten the MessageId from Peek Messages, and now wants to claim a specific message. This would allow more flexible sharing of queues. Without this it is difficult to support worker specialization (multiple workers monitor a queue, but not all workers can handle all messages). For us, the best current alternative requires creating A LOT of queues.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  14. Queue.PeakLast() required

    It would be good to provide to peak last message in Queue.

    When a job enqueue messages for processing, last item can be a start point for a new job. It could be perfect combination with Azure WebJobs.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add a queue permission that prohibits clearing the queue while allowing reading and deleting individual messages

    Any SAS that allows processing messages from a queue inherently includes the permission to clear the queue. In scenarios with multiple consumers from a single queue, this is almost always undesirable.

    In IoT scenarios, this can be disastrous. You may have thousands of devices processing messages from a single queue. None of those devices needs the ability to clear the queue. A single compromised device can immediately disrupt the entire process. Even worse, if you use the REST API, a simple bug that results in a device omitting the parameters that identify the message to be deleted will be interpreted…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  16. allow to create queue using arm template

    We need to create queue using arm template. Now we cannot deploy our product where Azure Functions use this queue.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add functionality to check for queue with no entries (including invisible entries)

    When a queue becomes empty I want to kick off some processing. However queue empty does not equal complete empty as there might be invisible objects on the queue that might come back. Thus it is not truly empty.

    Functionality to check a queue _really_ empty i.e. no objects invisible or visible would be very useful.

    Currently what I'm using is "peekMessage" returning null but this returns null even if there are invisible objects on the queue

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  18. Make SourceKey; DestKey; SAS More Accessible From The Storage Container Interface & Improve Written Doc For

    The web site documentation for Windows Azure Powershell is incomplete and most tasks needed for getting keys , SAS and or journal files should be accessible from the storage contained management interface of Azure on line...

    Active Directory Functionality should be able to run with a proxy domain designations until formal domains can be obtained and or domains should be sold and generated on demand....

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  19. SSMS Crashes when using Query Store dashboards

    Bug.. for instance, if you select "Regressed Queries" and then change the Configuration to show Recent: Last 2 days, and History: Last 2 weeks, while hovering or selecting different query id's, SSMS will crash, close and reopen.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Queues  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base