Configuration: Service Levels: Mappings
Overview
Use this page to map business services to the service-level objectives that govern them. A business service is a system or workflow you monitor for performance and availability; an objective sets a measurable target, such as an availability percentage or response-time threshold. Mapping decides which objectives count toward a given service's evaluation.
The service must already exist on the Services page, and each objective must already have a target defined on the Objectives page, before you can map them here. Mappings you enable feed the service's evaluated health, which downstream dashboards, violation tracking, and status pages read from. Objectives left unmapped, or set to disabled, play no part in that evaluation.
On this page you select a service, review the objectives tied to it alongside their targets, and set each to Not mapped, Enabled, or Disabled before saving. Refresh reloads the last saved state, and switching services without saving first discards any pending changes.
Key concepts
- business service - A system or workflow you monitor for performance and availability, selected from the Service dropdown on this page. (related: Configuration: Service Levels: Services)
- objective - A measurable target, such as an availability percentage or a response-time threshold, that a service must meet. Objectives are created and thresholded on the Objectives page before they can be mapped here. (related: Configuration: Service Levels: Objectives)
- mapping - The link between a business service and an objective, set to Not mapped, Enabled, or Disabled. Enabled mappings count toward the service's evaluated health; Disabled mappings are kept on record but excluded from evaluation. (related: Service Levels: Dashboard)
When to use it
- You're onboarding a new business service and need to decide which objectives should evaluate it.
- You created a new objective and need to attach it to one or more services.
- You want to temporarily pause an objective's effect on a service without deleting the mapping.
- You're auditing which objectives currently govern a given service before changing alerting or policies.
- You're comparing mapping configurations across different services.
Before you begin
- The business service you want to configure already exists, created on Configuration: Service Levels: Services.
- The objective(s) you want to map already exist with a defined target threshold, created on Configuration: Service Levels: Objectives.
- Any mapping changes you made on a previous visit to this page for another service were saved; unsaved changes are discarded when you switch services.
Common workflows
Map an objective to a service
Persona: Service-level admin configuring a new service
- Select the business service you want to configure from the Service dropdown.
- Expect: The panel reloads to show that service's objectives, each with its target and current mapping status.
- Choose Enabled from the status dropdown for the objective you want to apply to this service.
- Expect: The dropdown updates to show Enabled; the change is not yet saved.
- Select Save mappings.
- Expect: The mapping is persisted; reopening the page or reselecting the service shows the objective still set to Enabled.
Verify: The objective's dropdown reads Enabled after a refresh or page reopen, and the service's evaluated health on Service Levels: Dashboard begins factoring in that objective's target.
Exclude an objective without losing its mapping
Persona: Admin pausing an objective during planned maintenance
- With the affected service selected, change the objective's status dropdown from Enabled to Disabled.
- Expect: The dropdown shows Disabled.
- Select Save mappings.
- Expect: The mapping is saved as Disabled.
Verify: The objective no longer affects the service's evaluated health, but its mapping and target remain visible on this page set to Disabled rather than removed, so it can be re-enabled later without recreating it.
Steps
Step 1
Open the Mappings page under Configuration, Service Levels.
Expected result: The page loads with Service set to Digital Workspace (Prod) and lists its two objectives, Portal availability (Availability - 99.9%) and Portal response under 2 s (TransactionSla - 95%), both showing Not mapped; a Credentials expiring notice floats over the top of the page.
This is the starting point for deciding which objectives should govern the selected service.
- Service dropdown defaults to the last-viewed business service.
- Each objective row shows its target subtitle (for example, Availability - 99.9%) next to its status dropdown.
-
Save mappings is available even before you change anything.
Step 2
Select Refresh in the page header.
Expected result: The panel reloads the saved mapping state for Digital Workspace (Prod); both objectives still show Not mapped because nothing was changed, and the floating Credentials expiring notice is no longer shown.
Refreshing confirms you're working from the latest saved mappings before editing or saving.
-
Refresh is the circular-arrow icon in the page header, separate from Save mappings.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Service | Selects which business service's objective mappings you're viewing and editing. Switching to a different service replaces the objective list with that service's objectives and discards unsaved changes for the service you're leaving. | dropdown, single select | No | Digital Workspace (Prod) |
| Portal availability | Sets the mapping status for the Portal availability objective (target: Availability - 99.9%) against the selected service. Not mapped means the objective isn't linked to this service; Enabled means it's linked and counts toward the service's evaluated health; Disabled keeps the link on record but excludes it from evaluation, useful for pausing an objective without losing its configuration. | dropdown, single select | No | Not mapped |
| Portal response under 2 s | Sets the mapping status for the Portal response under 2 s objective (target: TransactionSla - 95%) against the selected service, using the same Not mapped, Enabled, Disabled choices as Portal availability. | dropdown, single select | No | Not mapped |
Controls reference
Refresh
Reloads the mapping panel for the currently selected service from the server.
When to use: Use it to confirm you're viewing the latest saved mappings, for example after another admin may have changed them.
Side effects: Read-only: it does not save pending dropdown changes, and reloading replaces unsaved edits with the last saved values.
Save mappings
Persists the Not mapped, Enabled, or Disabled status set for each objective under the currently selected service.
When to use: Use it after changing one or more objective status dropdowns.
Side effects: Mutating: updates which objectives count toward this service's evaluated health going forward.
Close (credentials notice)
Dismisses the floating Credentials expiring banner.
When to use: Use it to hide the reminder without acting on it immediately.
Side effects: Read-only: only hides the banner for this view; it does not reissue or renew the expiring credential.
Verify the result
After selecting Save mappings, the status dropdown for each objective you changed shows Enabled or Disabled instead of reverting to Not mapped. Reselect the same service from the Service dropdown, or reopen the page, and the values you set persist rather than resetting. If you enabled a mapping, the service's evaluated health on Service Levels: Dashboard should start reflecting that objective's target. If a dropdown reverts to Not mapped after navigating away, the change was never saved.
Troubleshooting
- Symptom: Switching the Service dropdown clears a status change you just made. Fix: Select Save mappings before switching services; unsaved mapping changes for the service you're leaving are discarded on switch.
- Symptom: An objective's dropdown still reads Not mapped after you set it to Enabled. Fix: Confirm you selected Save mappings rather than Refresh; Refresh reloads the last saved state and drops unsaved edits.
- Symptom: An objective you mapped doesn't appear to affect the service's evaluated health. Fix: Check whether its dropdown is set to Disabled rather than Enabled; Disabled mappings are kept but excluded from evaluation.
- Symptom: A Credentials expiring banner covers part of the Mappings panel. Fix: This notice is unrelated to mappings; reissue the referenced token from Configuration: Credential Profiles or dismiss the banner with its close icon.
- Symptom: No objectives appear for the selected service. Fix: Confirm at least one objective has been created and targeted for this service on Configuration: Service Levels: Objectives.
Related articles
- Prerequisite: Configuration: Service Levels: Services - the business service must exist before you can map objectives to it
- Prerequisite: Configuration: Service Levels: Objectives - each objective's target threshold is defined here before it can be mapped
- Next step: Service Levels: Dashboard - shows the evaluated health produced from the mappings set on this page
- See also: Configuration: Credential Profiles - where the token referenced by the credentials-expiring notice is reissued