The indispensable tool for Azure Service Bus:
|*||Also works for MSMQ, RabbitMQ, and ActiveMQ. Everything from the same app!|
With QueueExplorer you can dig into your queues and see which message went where, whether they were correctly formatted, with correct headers and settings, etc.
Multiple viewers are at your disposal: JSON, XML, WCF, Hex, text with different encodings...
With QueueExplorer you can test individual pieces of your solution, or even simulate third party messages going in or out. You can create and edit test messages, send one by one or bunch of them together.
Send thousands of messages for performance testing to see how system handles that load.
If something is wrong, QueueExplorer is the fastest and easiest way to investigate and fix incorrect, poison, or failed/deadletter messages.
Check if some of queues are growing too large, if there are messages in deadletter queues, etc. With autorefresh functionality see how entire system works in near real time.
QueueExplorer allows you to quickly find messages you're interested in. Professional edition allows you to even extract your business data from within messages using XPath, JSON, or Regex, and to immediately see e.g. invoice totals, etc.
Backup messages to files, or move/copy them to another queue.
Azure Service Bus has two special kinds of messages - deferred and scheduled, which your applications normally don't see. With QueueExplorer you can check these messages, put them back in queue or reschedule them for another time.
This can be used to migrate queues (and other objects) to another namespace, e.g. to propagate from development to production. Or just to compare and see which changes were made. Or to backup schema before changes are made. You can also duplicate queues with all their settings on the same server (Professional).
|Scheduled and deferred messages|
|Schema (metadata) operations|
|Extract business data from messages|
|+ All from Standard|
QueueExplorer is used in thousands of companies worldwide, solving their MSMQ, Azure Service Bus, RabbitMQ, and ActiveMQ problems.