Tharga.MongoDB.Blazor 2.13.0

Tharga.MongoDB.Blazor

Drop-in Blazor admin UI for Tharga.MongoDB. Renders the live monitoring data already captured by the core package — collections, calls, indexes, queue metrics, connected clients — as Razor components you can host on any admin page in your app.

Install

dotnet add package Tharga.MongoDB.Blazor

The components depend on the data flowing through Tharga.MongoDB's IDatabaseMonitor, so you need that package registered as well:

builder.AddMongoDB();

Then drop the components onto a Blazor page — they auto-discover the monitor via DI:

@page "/database"

<RadzenCard Style="margin-bottom: 6px;">
    <Tharga.MongoDB.Blazor.MonitorToolbar />
</RadzenCard>

<RadzenTabs>
    <Tabs>
        <RadzenTabsItem Text="Collections">
            <Tharga.MongoDB.Blazor.CollectionView />
        </RadzenTabsItem>
        <RadzenTabsItem Text="Calls">
            <Tharga.MongoDB.Blazor.CallView />
        </RadzenTabsItem>
        <RadzenTabsItem Text="Clients">
            <Tharga.MongoDB.Blazor.ClientsView />
        </RadzenTabsItem>
    </Tabs>
</RadzenTabs>

Components

• <MonitorToolbar /> — top-bar controls: configuration switcher, reset calls, reset cache.
• <CollectionView /> — table of every registered collection with status, document count, indexes, and per-collection drill-down dialog. The Source column shows which sources have accessed each collection; hover it for the full set with access to the same physical database (server + database name) — including sources that could reach it via a different configuration — with a (+N) hint when there are more than have accessed it.
• <CallView /> — every database call captured by the monitor, with filter, sort, explain plan, and timing.
• <ClientsView /> — connected monitoring agents. Useful with Tharga.MongoDB.Monitor.Server when aggregating multiple agents; shows each agent's forwarding config (call-forwarding on/off, queue interval, storage mode).
• <QueueView /> — a cluster → pool → source breakdown of open connections (summed per cluster vs each cluster's limit), with queue/executing folded in, plus depth/wait graphs with one line per pool (matching colours, no legend — the cards are the key).
• <ClusterConfigView /> — edit per-cluster settings at runtime: connection limit (Atlas tier picker or manual), display alias, and bar warn/danger thresholds. Persisted centrally (shared across instances) and read by <QueueView />.
• <ConfigurationsSelector /> — switch between configured ConnectionStrings entries when an app talks to multiple clusters.

The package is built on Radzen.Blazor — the same components and theming as the rest of your Radzen app.

Documentation

Full docs and configuration reference: github.com/Tharga/MongoDB.