v0.10.0

0.10.0 — 2026-09-03

The monitoring dashboard listed everything it watched. On a real estate that means a handful of queues worth looking at, buried under hundreds reading “0”. This release makes the list the work — and fixes a set of click-throughs that quietly did nothing.

Monitoring

• The dashboard opens on what’s carrying dead letters. Everything else — queues at zero, and ones not yet sampled — is behind a “carrying DL” chip you can switch off, and the list header always says how many of the total you’re seeing. A purged dead-letter queue keeps its row until retention catches up, which is why the list used to be mostly noise.
• The row sparkline follows the window you picked. It was pinned at 24 hours no matter what the 1h/6h/24h/7d/30d pill said, so “+5 in the last hour” sat next to a shape covering a day with nothing on screen admitting it.
• Slice the list by subscription, namespace, or entity type. Multi-select on each, with counts, and queues separable from topic subscriptions. Namespace choices narrow to the subscriptions you’ve ticked, so you can’t build a pair of filters that only ever returns nothing.
• Namespaces deleted in Azure leave the sidebar. A namespace removed in the portal stayed in the tree and stayed monitored, failing every check against a hostname that no longer resolves — and getting logged as a possible network outage. It’s now dropped as soon as Azure stops listing it.
• A quieter row. The severity rail down the left edge is gone; the same information was already in the colour of the row’s number.

Fixes

• Clicking a notification opens the right resource. If an alert, a finished operation, or a history entry named something outside the subscription you happened to be in, the click either did nothing at all or opened the correct tab on the wrong queue. Alerts in the bell, operation rows, the floating progress widget and the History pane all switch subscription first now, and only then land on the resource.
• Resending a subscription’s message goes to its topic. You can’t send to a subscription — the attempt sat there burning the full send timeout before failing, which read as contention rather than a wrong destination.
• Arrow-key selection stays on screen when you walk a long message list.
• The ⓘ popover hands over names. Name, parent topic, namespace and the full entity path, each with its own copy button, and all of it selectable if you’d rather drag.
• A session that never recorded its tenant repairs itself. If the tenant picker got skipped — the sign-in succeeded but listing tenants failed — everything looked healthy except the MCP tools, which refused with “No tenant selected in ViewBus”. The next launch fixes it, and anything indexed in the meantime, with nothing to click.
• Filtered counts no longer under-report. count_messages over MCP walked a single page before answering, and now groups a breakdown by more than dead-letter reason in the same pass.

Under the hood

• The index moved out of your roaming Windows profile. viewbus.db and the logs now live under %LOCALAPPDATA% instead of %APPDATA%. It’s a machine-local cache of one machine’s Azure estate — it grows well past 100 MB, and it had no business syncing between machines and slowing down every Windows login. Your existing index moves itself on first launch and is compacted on the way across, typically shedding a third of its size. Nothing to re-add, and settings, themes and stored connections stay exactly where they were. If you have a plugin reading the database file directly, look in %LOCALAPPDATA%\viewbus\ first and fall back to the old path; the /v1 discovery file has not moved.
• The database stops hoarding disk. Its write-ahead log had no size ceiling, so the one big transaction of a full re-index left a sidecar tens of megabytes larger than the database needed, permanently.
• Stale monitoring state is cleared. Health records for subscriptions you’d un-enrolled — or a tenant you’d left — stayed forever, still reporting failures nothing could clear.

All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.