How can we improve the Windows Azure Service Bus?

Journaling for Topics and Queues

The feature I've been missing most of all in Service Bus is Journaling as many other message brokers offers. We really need to track all messages flowing through Service Bus and be able to search for a specific message based on Message Properties. You might not need to supply a web-interface for this as long as all messages are stored, somewhere, like in table storage...

Is this a feature which is planned?

22 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Thomas L shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • GG commented  ·   ·  Flag as inappropriate

    Journaling OK, but what one needs to be able to debug and analyse svc bus problems is more like the trace levels providec by nlog or log4net. The svc bus user could simple provide an azure table storage name and set the desired "vervosity" level to trace every aspect of messages including things like "were all the messages that I put on the bus picked up" and how many messages did I put on the bus in the last 10 min...

Feedback and Knowledge Base