Configuration
Configuration is the setup hub for a WISdom account. It answers one question that no other screen answers directly: what still needs to be set up before WISdom can tell you what your SQL Server estate costs?
Everything Configuration links to can also be reached from Admin Console. The difference is framing. Admin Console is organized by screen, so you have to already know what you are looking for. Configuration is organized by readiness, so it tells you what is done, what is not, and what to do next. If you are setting up a new account, start here.
Find it under ADMIN in the left navigation, directly above Admin Console.
How the screen is organized
Section titled “How the screen is organized”Configuration groups setup into four areas. Each area heading carries a progress badge
showing how many of its cards are finished, for example 3 of 3, and a one-line
description of what the area controls.
| Area | Cards |
|---|---|
| Collection | Data Collectors, Resources, Credentials |
| Monitoring | Monitoring Profiles, Notification Channels, Silencing Windows |
| Reporting | Report Templates, Report Subscriptions |
| FinOps and Setup | Team, Integrations, Tags, Cost Management, Opportunity Policies |
The order is a dependency chain, not a preference. Monitoring has nothing to alert on until Collection is running, and Reporting has nothing to report until both are in place. Work top to bottom.
Unlike most WISdom screens, Configuration has no toolbar and no date-range picker. There is nothing to filter here, so Views, Tag, Filters, Reset, and Share do not appear.
Reading a card
Section titled “Reading a card”Every card follows the same pattern:
- An icon and the card name, for example Data Collectors.
- A status badge in the top right. See the state list below.
- A one-line description of what the card controls, followed by a Learn more link into the relevant documentation page.
- A count box showing the current total for that item, for example the number of collectors installed, resources connected, or credentials stored. The label names what is being counted.
- Two buttons. View opens the full screen for that item. Add creates a new one directly, and is labelled for the thing it creates: Add Collector, Add Resource, Add Credential, Add Profile, Add Channel, Add Window, Add Template, Add Subscription, Add Member, Add Integration, Add Tag.
Card states
Section titled “Card states”| Badge | Meaning |
|---|---|
| COMPLETE | The item is configured. At least one exists. |
| SET UP | Nothing is configured yet. This is the work still outstanding. |
A COMPLETE badge means the area is configured, not that it is optimal. Collection showing all cards complete still leaves you to confirm that every instance you care about is actually assigned to a collector and reporting in, which Configuration does not check for you. Use Collector Health and the latency columns on Data Collectors for that.
TODO(product): confirm whether any state exists between COMPLETE and SET UP (for example a partial or warning state when an item exists but is unhealthy). Only COMPLETE and SET UP were present in the captured tenant.
What each area sets up
Section titled “What each area sets up”Collection
Section titled “Collection”How WISdom gets data out of your environment. Nothing else in the product produces data until this area is complete.
- Data Collectors - install collectors and verify data is flowing. See Data Collectors.
- Resources - the SQL Server instances, databases, and cloud resources to monitor. See Resources.
- Credentials - stored service-account credentials WISdom uses to authenticate against each resource, where the collector’s own service account is not sufficient. See Credentials.
Before you start, check the host meets the OS, firewall, antivirus, and service-account prerequisites, and size the collection VM to the number of servers you intend to monitor. See Requirements - Installation and Accounts.
Monitoring
Section titled “Monitoring”How WISdom tells you when something is wrong, and who it tells.
- Monitoring Profiles - bundles of alert types and thresholds assigned by environment, so production can carry stricter rules than the rest of the estate. See Profiles.
- Notification Channels - where alerts get delivered: email, SMS, Slack, PagerDuty, Teams, or your ticketing system. See Notification Channels.
- Silencing Windows - suppress alerts during planned downtime so the team is not paged for expected maintenance. See Silencing Windows.
A notification channel is inert until an alert rule or a profile references it. Adding a channel is not the same as turning alerting on.
Reporting
Section titled “Reporting”How findings leave the product and reach people who do not log in.
- Report Templates - pre-built and custom report formats covering health, cost, capacity, and executive summary views. See Creating a Report Template.
- Report Subscriptions - schedule reports for automatic daily, weekly, or monthly delivery to a recipient list. See Creating a Report Subscription.
FinOps and setup
Section titled “FinOps and setup”The account-level settings that make the cost figures yours rather than defaults.
- Team - invite people to access dashboards, cost visibility, and health alerts. See Team.
- Integrations - connect ticketing, notification, and service-management tools. See Integration.
- Tags - create tag groups and assign resources, which is what drives cost grouping and alert logic. See Tags.
- Cost Management - your licensing, storage, wait-time, and server-type rates. See Cost Management.
- Opportunity Policies - policies for overrides, targeting, and custom configuration of opportunities. See Opportunities.
Cost Management is the card most worth not skipping. Every dollar figure in WISdom derives from the cost model, so leaving it at the shipped default rates means the spend numbers are directionally useful but not yours.
Who can use this screen
Section titled “Who can use this screen”TODO(product): confirm which roles can see Configuration and which can act on its cards. The role model is documented on Team, but the permission behaviour of this screen specifically is unverified. Do not assume it matches Admin Console until someone checks.