Service Levels: Dashboard
Overview
Use this page to review Service Levels setup readiness and resolve the configuration gaps that block it. Service Levels is LoadGen's module for tracking whether your systems meet defined performance and availability targets, called objectives; this dashboard answers, at a glance, whether enough has been configured for that tracking to work, including how many services and objectives exist, whether they're linked, and whether a database is selected to store the resulting history.
Before this dashboard shows meaningful data, services must exist on Configuration: Service Levels: Services, objectives must be defined on Configuration: Service Levels: Objectives, and the two must be linked on Configuration: Service Levels: Mappings; a snapshot datasource is chosen on Configuration: Service Levels: Storage. Once those pieces are in place, the compliance data this dashboard summarizes flows into Service Levels: Health and Service Levels: Violations for ongoing monitoring.
From here you can review KPI cards summarizing coverage and readiness, a Service coverage table listing every service and its mapping state, a Setup checklist of outstanding items, and a Source mix panel showing which monitoring types feed the data. Buttons let you refresh the view, jump to service management, or start a new objective.
Key concepts
- Service - A system or application tracked by Service Levels, such as a published desktop or application you load-test or monitor. (related: Configuration: Service Levels: Services)
- Objective - A target threshold (an SLO) defining the performance or availability level a service must meet. (related: Configuration: Service Levels: Objectives)
- Mapping - The link between a service and one or more objectives that tells Service Levels which target thresholds apply to that service's incoming data. (related: Configuration: Service Levels: Mappings)
- Snapshot store - The SQL Server or PostgreSQL database where Service Levels saves calculated snapshots of compliance over time. (related: Configuration: Service Levels: Storage)
- Readiness - A computed status showing whether the basic setup (a selected datasource and fully mapped services) is complete.
When to use it
- You want a quick status check on whether Service Levels is fully configured before relying on its compliance data.
- A new service or objective was just created and you need to confirm it's reflected here and properly mapped.
- You're troubleshooting why Service Levels: Health or Service Levels: Violations shows no data for a service.
- You need to find the single next configuration step blocking readiness, for example selecting a snapshot datasource.
- You want to see which monitoring types, such as Uptime Monitoring, are contributing data to Service Levels.
Before you begin
- At least one service exists on Configuration: Service Levels: Services; otherwise the Service coverage table and the Services KPI stay empty.
- At least one objective is defined on Configuration: Service Levels: Objectives for the Objectives KPI to be non-zero.
- You have configuration access to Service Levels; the Manage and Set up new SLO buttons require that access to take effect.
Common workflows
Check readiness and resolve the first open setup item
Persona: Load-test admin
- Open the Service Levels: Dashboard page.
- Expect: The KPI cards, Service coverage table, and Setup checklist load with current data.
- Review the Readiness KPI card.
- Expect: The card shows Needs setup with a count of open items, such as 2 open items.
- Select the first item in the Setup checklist, Select a ServiceLevels datasource.
- Expect: The browser navigates to the Service Levels storage configuration page where you can choose a SQL Server or PostgreSQL datasource.
Verify: Return to the dashboard and select Refresh; the Storage and Snapshot Store KPI cards show the selected database instead of Not selected, and the open-items count on Readiness decreases by one.
Map an unmapped service to an objective
Persona: Load-test admin
- Locate a service marked Unmapped in the Objectives column of the Service coverage table.
- Expect: The row's Objectives and State columns both show warning-styled badges, Unmapped and Needs mapping.
- Select Mappings in the Service coverage panel header.
- Expect: The browser navigates to the Service Levels mappings configuration page.
- Create a mapping linking the service to one or more objectives, then return to the dashboard.
- Expect: The Service coverage table row's State column no longer shows Needs mapping, and the Service Coverage KPI ratio increases.
Verify: The Service Coverage and Mapped Objectives KPI progress bars advance past zero, and the row's Objectives column lists the mapped objective instead of Unmapped.
Steps
Step 1
Open the Service Levels: Dashboard page.
Expected result: The page loads showing seven KPI cards (Services, Objectives, Storage, Readiness, Service Coverage, Mapped Objectives, Snapshot Store), a Service coverage table listing each configured service, a Setup checklist panel, and a Source mix panel.
This overview is the starting point for judging whether Service Levels is fully configured before you rely on its compliance data.
- Readiness shows Needs setup with a count of open items and a chevron to drill into them.
- The Service coverage table shows Unmapped and Needs mapping badges for any service not yet linked to an objective.
-
Refresh, Manage, and Set up new SLO sit in the page header for reloading data or jumping to configuration.
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| Services | Total count of services currently configured for Service Levels tracking. | Compare this count against the services you expect to track; a lower-than-expected number means a service is still missing from Configuration: Service Levels: Services. |
| Objectives | Total count of objectives (SLOs) defined, regardless of whether they're mapped to a service yet. | An objective only becomes useful once it's mapped; check Mapped Objectives for how many of this count are actually applied. |
| Storage | Whether a snapshot datasource has been selected for storing Service Levels history. | Not selected means no database is chosen yet; select the Add a ServiceLevels datasource link under this card to fix it. |
| Readiness | Overall setup status aggregating every open configuration item that still blocks full Service Levels operation. | Needs setup with a nonzero open-item count means the items listed in the Setup checklist still need action; select the card's chevron to see them. |
| Service coverage | Ratio of services that have at least one mapped objective out of the total configured services. | The progress bar fills as more services get mapped; 0 of any total means none of your services are mapped yet. |
| Mapped objectives | Ratio of objectives actively applied to at least one service out of the total defined objectives. | A low ratio against a nonzero Objectives count means objectives exist but haven't been linked to a service yet on the Mappings page. |
| Snapshot store | Mirrors the Storage status and names the supported database types for snapshot storage. | Supported options are SQL Server or PostgreSQL, chosen on Configuration: Service Levels: Storage; Not selected means neither is configured. |
| Service | Name of the tracked service with its environment shown underneath. | Use the sub-label to distinguish services of the same name running in different environments. |
| Objectives | Shows which objectives, if any, are mapped to this service. | Unmapped means no objective is linked to this service yet; once you create a mapping, this column lists the mapped objective instead. |
| Sources | Shows the monitoring or testing sources feeding data into this service. | A dash means no data source is feeding this service yet, which blocks any compliance calculation for it. |
| State | Overall readiness state of this specific service row. | Needs mapping means this service requires at least one objective mapping before Service Levels can calculate compliance for it. |
| Source mix - Uptime | Count of Uptime Monitoring sources currently contributing data to Service Levels, against the total expected. | The progress bar reflects how much of the connected Uptime Monitoring data is actually in use; a near-empty bar means most of it isn't tied to a mapped service yet. |
Controls reference
Refresh
Reloads the KPI cards, Service coverage table, Setup checklist, and Source mix panel with current data.
When to use: After you've made changes on Configuration: Service Levels: Services, Objectives, Mappings, or Storage and want this dashboard to reflect them.
Side effects: Read-only; it re-fetches the current state and does not change any configuration.
Manage
Navigates to the Service Levels services configuration page.
When to use: When you need to add, edit, or remove the services tracked by Service Levels.
Side effects: Navigation only from this page; service changes happen on the target page.
Set up new SLO
Opens the guided setup for defining a new service-level objective.
When to use: When you need a new target threshold that doesn't exist yet, and want a guided flow rather than configuring each piece manually.
Side effects: Navigation to a setup wizard; nothing is created until you complete it.
Mappings
Opens the Service Levels mappings configuration page listing all service-to-objective links.
When to use: When the Service coverage table shows Unmapped or Needs mapping on a row and you need to link it to an objective.
Side effects: Navigation only; mapping changes happen on the target page.
Add a ServiceLevels datasource
Opens the Service Levels storage configuration page to choose a SQL Server or PostgreSQL database for snapshots.
When to use: When the Storage KPI card shows Not selected.
Side effects: Navigation only; the database isn't connected until you configure it on the target page.
Select a ServiceLevels datasource
The Setup checklist entry that opens the same storage configuration page as Add a ServiceLevels datasource.
When to use: When Readiness lists it as one of the open items blocking setup.
Side effects: Navigation only.
Map every service to one or more objectives
The Setup checklist entry that opens the Service Levels mappings configuration page.
When to use: When Service Coverage is below its total and Readiness lists mapping as an open item.
Side effects: Navigation only.
Readiness card
The chevron on the Readiness KPI card opens a detailed view of the open items contributing to the Needs setup status.
When to use: To see exactly which items block readiness before clicking through to fix them one by one.
Side effects: Read-only; navigation or expansion, no configuration changes.
Start setup
Launches the guided Service Levels setup wizard; appears in place of the Service coverage table when no services exist yet.
When to use: For first-time setup when Services is at zero.
Side effects: Navigation to a setup wizard; nothing is created until you complete it.
Or configure manually
Navigates directly to the services configuration page instead of the guided wizard; appears alongside Start setup in the empty state.
When to use: When you prefer to configure services, objectives, and mappings by hand rather than through the wizard.
Side effects: Navigation only.
Verify the result
The review is complete when you can state exactly what's blocking readiness, whether it's an unmapped service, missing objectives, or no snapshot datasource. On a fully configured instance, Readiness shows no open items, Service Coverage and Mapped Objectives both reach their total (for example 1/1 and 2/2), and Storage and Snapshot Store display the chosen database instead of Not selected. No row in the Service coverage table shows an Unmapped or Needs mapping badge. If a KPI still shows a gap after you've made a change elsewhere, select Refresh before assuming the fix didn't take.
Troubleshooting
- Symptom: Readiness still shows Needs setup after you selected a datasource and created mappings. Fix: Select Refresh; this page only re-evaluates readiness when it reloads data, it doesn't update live while you work on other pages.
- Symptom: Storage and Snapshot Store both still show Not selected after configuring a database. Fix: Confirm you saved the datasource on the Service Levels storage configuration page rather than only testing the connection there.
- Symptom: A service stays marked Unmapped and Needs mapping in the Service coverage table. Fix: Select Mappings and confirm the mapping links that specific service to at least one objective; a mapping created for a different service won't clear this row.
- Symptom: Set up new SLO or Manage appear to do nothing when selected. Fix: Confirm your account has Service Levels configuration permissions; viewing this dashboard doesn't require the same access as changing its setup.
- Symptom: Service Coverage or Mapped Objectives shows a ratio of zero even though objectives exist. Fix: An objective only counts once it's actively mapped to a service; check Mappings rather than the objectives count for the missing link.
Related articles
- Prerequisite: Configuration: Service Levels: Services - services summarized on this dashboard are created here
- Prerequisite: Configuration: Service Levels: Objectives - objectives counted in the Objectives KPI are defined here
- Next step: Configuration: Service Levels: Mappings - clear Unmapped and Needs mapping rows by linking services to objectives here
- Next step: Configuration: Service Levels: Storage - select the snapshot datasource this dashboard checks for
- See also: Service Levels: Health - once services are mapped, ongoing objective compliance is tracked here
- See also: Service Levels: Violations - review SLO breaches once services are mapped and storage is configured