Changelog

4.47.0

Updated all dependencies to latest versions. Fixed bug alert dispatch, so notification groups are properly targeted.

4.34.0

Fleet Manager can now work as a "timeout manager", i.e. it can serve as the persistence required for Rebus to be able to defer messages ("send them into the future") regardless of which transport you're using.

It requires Rebus.FleetManager plugin version 7.0.0-b03 (at least), because it requires an additional configuration extension: .Timeouts(t => t.StoreInFleetManager())

4.21.0

Better graphical visualization of subscriptions + ability to filter queues/topics.

4.20.0

We have recorded calls to await bus.Subscribe / await bus.Unsubscribe for a couple of versions of the driver now, and this version of Fleet Manager is now capable of displaying topics and bound queues in a table, as well as in a simple graphical visualization.

Look for it under Overview/Subscriptions. 🙂

4.8.9

Moved projections queue status, machine status, and bus instance info, to be in-mem.

Lazy-loading of charts to avoid freezing the screen when loading many of them.

Lots of small optimizations.

4.4.0

Refreshed UI under Failed Messages for adding filters.

Various optimizations on the backend: Cleaned up unused views, more aggressive expiration of in-mem projections, etc.

4.1.0

External API has been added. Visit Team Setup/External API and generate an API token, and then follow the link to the API docs page to get started. 🙂

4.0.51

OK we're moving quickly these days!! 🤠

Fleet Manager v4 is the first to be based on .NET Core 3.1 and a completely modernized foundation!

It went live on Wednesday the 23rd of September.

It has seen a tremendous amount of changes – too many to mention, actually – so we'll just leave it at that.

3.9.6

New shell that leaves more horizontal room for stuff, new overview with more information, filtering for archived messages, and more. 🤩

3.7.0

The histograms on the overviews over queue/machine/bus instance activity can now display activity for the last 7 days.

Alerts now work, so that their states are changed when you archive or mute them.

Alerts can be automatically archived when you retry their failed messages if you check the "Archive associated alerts" checkbox. 🙂

3.6.0

Slack channel webhooks can now be added under the "Integrations" tab under your team, and then alert rules can be configured to make use of them. 😎 The alerts page still needs some work, though.

You can read more on the Slack integrations doco page.

3.4.0

Redone message auditing page. 📜 When message auditing level is set to FULL, messages are now archived in GZIPped JSONL files every day – they can then be downloaded from the "Auditing" page in Fleet Manager.

You can read more on the documentation wiki.

3.3.2

Migrate backend to Kafka/Azure Event Hubs. Add ability to see overview charts for last 24h, 1h or 10 minutes. Add C#-aware hightlighting of stacktraces. Add deep link-capability for messages. And more. 🙂