Everything the dashboard does
Real screenshots, no mockups. Each tag shows the minimum edition that includes it.
Estate Overview
A compact chicklet grid of every monitored server, colored green/yellow/red at a glance, filterable by engine and environment. Built to stay readable at a few hundred servers, not a dozen.
How it works
- Add servers one at a time, import from a SQL Server Central Management Server, or bulk-load a CSV/XLSX inventory template.
- Switch between five layouts — Signal Wall, Fleet Grid, Command Deck, Inventory, DB Inventory — with the tab bar; each reads the same underlying data differently.
- Checks run automatically on a background cycle, or click Refresh now to force an immediate pass across the whole estate.
- Click any server to drill into its own Server Detail page.
DB Inventory
Every server in Estate Overview expands to its own list of databases — state, size, and live connection counts — without eagerly querying every database on every refresh. A big SQL Server with dozens of databases stays fast: nothing is queried until you actually open its row.
How it works
- Click the caret next to any server on the DB Inventory tab to lazy-load its databases.
- Click Run checks on any database row for real Ok/Warning/Critical checks scoped to that one database — other rows stay untouched until you ask for them.
- Checks that have already run show as severity chicklets right in the row; a database you haven’t checked yet still just shows the trigger button, so you can see at a glance what’s been looked at.
Database Health
Click any database in DB Inventory to open its own two-column health page: real severity-based checks on the left, a feature inventory on the right — which optional engine features (partitioning, TDE, sequences, and dozens more) this specific database actually uses. 67 checks across all four engines, each tunable on the Thresholds page exactly like server-level checks.
How it works
- Checks show the same short severity chicklet used everywhere else in the app, plus the full check name, its status, and a plain-English description — hover a chicklet for the underlying check key.
- Facts only list the categories that exist on that engine at all — no placeholder "not applicable" rows for features Postgres or MySQL simply don’t have.
- A fact currently in use is highlighted in green, so a busy database’s real feature footprint stands out from the page at a glance.
Server Detail
Drill into any server for a four-panel dashboard of its checks — raw values or a detail grid, your choice, per panel.
How it works
- Click a server anywhere in Estate Overview to open its detail page.
- Toggle any panel between a raw-value view and a full detail grid independently of the others.
- Refresh just this one server on demand, without waiting for the fleet-wide cycle.
- Edit takes you straight to that server’s connection settings if something needs to change.
Custom Dashboards
Drag-and-drop panels — stat tiles, gauges, bar gauges, pie charts, time series, tables — built from your own queries against any monitored server, with per-panel warning/critical thresholds. Every engine ships with a real default layout to start from.
How it works
- Open Custom Dashboards from any server’s detail page — a real default board is already there for your engine.
- Edit Board to add or reposition panels, then Edit Panel to write the backing query and pick a visualization.
- Set a warning/critical threshold on any panel so it colors itself the same way a built-in check would.
Add & edit servers
Test Connection before you save, import from a SQL Server Central Management Server, or bulk-import a CSV/XLSX inventory template.
How it works
- Add Server for a single instance — fill in host, port, engine, and credentials, then Test Connection before saving.
- Import from CMS to pull every instance already registered in an existing SQL Server Central Management Server.
- Import from File to bulk-load a CSV/XLSX inventory using the provided template — useful for a first-time migration from another tool.
- For Oracle specifically, point the database/service field at the CDB root (not one PDB’s own service) if you want every pluggable database visible.
Roles & users
Seven built-in roles — from read-only viewer to full admin — each with its own execution capabilities and page access, issued as real OpenID Connect (OIDC) claims. Personal is single-user; team accounts start at Professional.
How it works
- Users page (admin-only) → Add User with a username, email, password, and role.
- Change a user’s role inline at any time; the built-in first-run admin account can’t be renamed, demoted, or deleted.
- Roles are enforced as real OpenID Connect (OIDC) claims on the API itself, not just hidden in the UI — a Viewer can’t reach an admin-only endpoint by guessing the URL.
- Edit lets an admin reset any user’s password or change their email directly, without that user needing to self-service it.
Alerts & thresholds
Tune warning and critical thresholds per check, per environment — production and dev don’t have to alert the same way. Email/Pushover/Slack/Teams routing, suppression rules, and the alerts-database migration wizard are all part of the same alerting bundle.
How it works
- Thresholds page → pick a check, set its Warning and Critical values per environment.
- Settings → Notifications wires up Email, Pushover, Slack, and Teams; recipients can be scoped to specific servers and checks so people only hear about what they own.
- Alerts fire once on crossing into Warning/Critical, and again on recovery — not a repeat every cycle while it stays bad.
- Alert Suppressions mutes one check on one server temporarily, without touching its global threshold.
Reports
A built-in library of diagnostic scripts drawn from a working DBA’s own collection — real, battle-tested insight into your environment, not generic boilerplate. Run them point-in-time or on a schedule across the fleet, export to PDF, and add your own scripts to the same library alongside the built-ins.
How it works
- Reports page → Run Now for a point-in-time report, or Schedule for a recurring one.
- Every report exports to PDF for sharing outside the app.
- Add Script drops your own query into the same library the built-ins live in — same run/schedule/export path for it as everything else.
Credential Manager
A fleet-wide view of stored credentials, distinct from the per-server storage every edition already gets — register the same login separately per environment (production, staging, dev, and beyond), track password age, and push a password change across every selected server in one bulk action, exactly the workflow real password-rotation policies demand.
How it works
- Credential Manager lists every account it knows about across the fleet, with password age called out.
- Pick an action (create, change password, delete, or create-or-alter), an account name, and a password, then multi-select the servers it applies to.
- One bulk action runs the same operation against every selected server, with per-server success/failure reported back — no more re-typing the same password change fifty times.
- Usernames are validated against each engine’s own quoting rules before anything runs, so a bulk action can’t become an injection vector.
Deployment tooling
Fetch and stage the DBA scripts you already trust — sp_WhoIsActive, Brent Ozar’s First Responder Kit, Ola Hallengren maintenance solution — straight from their upstream sources. Or upload your own trusted scripts into the same catalog for centralized, repeatable deployment across the fleet.
How it works
- DBA Deployment’s Recommended Third Party row fetches sp_WhoIsActive, the First Responder Kit, and Ola Hallengren’s maintenance solution straight from their upstream sources, with automatic Linux/Windows detection for SQLWATCH.
- Upload Script adds your own trusted script into the same catalog, alongside the built-ins.
- Multi-select servers and Deploy runs the chosen script against every one of them, with audit logging on every execution.
Every outbound call, itemized
The "zero telemetry" claim, made checkable: Settings lists every network call this app makes on its own — patch-baseline fetches, third-party script downloads — each with its own on/off switch. Nothing about your estate is ever sent off-box.
How it works
- Settings → Telemetry lists every outbound call the app makes on its own — SQL Server/MySQL/Oracle patch-baseline fetches, third-party deployment script downloads — each with its own on/off toggle.
- Turning one off just stops that specific feature from calling out; nothing else about the app changes.
- Settings → Updates adds a separate, on-demand version check — no license key, fingerprint, or usage data is ever sent, and nothing auto-downloads.