Fleet Manager is part of the Rebus Pro offering, and it is available now 🙂 if you want to get access to Fleet Manager now, please go to the Rebus Pro page and get in touch using the information found there.
While it is nowhere near finished yet, it can still be pretty useful – take a look at the screenshots on this page to get a glimpse.
When you sign in, you are greeted by the overview, where you can quickly get an overview of today’s activity on accounts accessible to you:
When you select an account, you are taken to the queues overview, where you can see which queues are processing messages – the green lines are successfully processed messages, and the bars indicate exceptions (i.e. retries) and messages moved to Fleet Manager with yellow and red stacked bars respectively:
You can even go and see individual Rebus bus instances, the time of their last heartbeat and/or recorded operation, which machine they’re hosted on, etc.:
and then, if we select an instance, we can even see (and change!) how many worker threads it is using, and see a log of stuff that has happened to it:
One of my favorite features is the sagas overview – here we can see (and filter) sagas:
and then if we click one, we can see all recorded state snapshots, including which message caused the saga to end up like that:
Last (but not least!): If one or more messages have failed, they are no longer stored in a “dead-letter queue” somewhere, they get stored in Fleet Manager, causing the appearance of a red dot:
Then you can go to the “Failed Messages” overview and apply the necessary filters…
…possibly inspect the message contents and ponder over the exception details…
…and then you can select the relevant messages and return them to their source queues to be retried.
And YES: Fleet Manager’s return-to-source-queue function works, no matter which transport you are using!
Please take a look at Rebus Pro if you think you can use this 🙂