---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Create SLOs, SLIs, and error budget policies

# Create SLOs, SLIs, and error budget policies {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Define service level objectives (SLOs), service level indicators (SLIs), and error budget policies to monitor service health. These tools help you and your teams track performance and respond when needed.

## Vorbereitungen

To send notifications when an error budget policy is breached, your team must have a notification destination configured. You can check by navigating to Teams\[Your team\]SLO Notification destinations in Service Operations Workspace. For more information, see [Create a notification destination in SRM](https://servicenow-prod.fluidtopics.net/RvI~JHcRsPQgy8H1s7uDvA "Set up notification destinations to help keep teams informed about service reliability.").  
Hinweis:  
By default, the outage data source for SLIs includes unplanned and degradation outages. Administrators can include planned outages by adding `planned` to the `sn_sow_slo.outage_supported_types` system property value.

Role required: srm_admin, srm_manager, or srm_responder

## Warum und wann dieser Vorgang ausgeführt wird

Create SLOs, SLIs, and error budget policies to monitor service health and help make sure that your services support business goals.

In Service Reliability Management (SRM), an SLO must have at least one SLI. SLIs can be filtered to a service or configuration item (CI) within the parent service hierarchy. Filtering an SLI to a CI can help you more
accurately track service health and identify root causes faster.

Each SLI can be associated with only one SLO, helping prevent conflicting performance expectations.  
Hinweis:  
SLOs can also be generated automatically using the SLO creator agent. For details, see [Generating service level objectives](https://servicenow-prod.fluidtopics.net/1FBnfrJzlZ2mZKw7qllaIw "Use the service level objective (SLO) creator agent to auto-generate SLOs for Service Reliability Management (SRM) services and configuration items (CIs). The agent can help teams adopt SLOs faster and monitor service performance.").

## Prozedur

1. Navigate to WorkspacesService Operations WorkspaceServices (![Services icon]()).
2. On the Services page, select the service you want to monitor, then select the Reliability metrics tab and select Add SLO \& SLI.
3. In the Service Level Objective (SLO) form, fill in the fields for your SLO and select Next.  
   For information about the SLO fields, see [Create SLO form](https://servicenow-prod.fluidtopics.net/hWBYHnaNO15~DliMnyIqjg "Learn about the available fields for adding a service level objective (SLO) to Service Reliability Management.").
4. In the Service Level Indicators (SLI) form, select the data source for your SLI.

   | Data source | Description |
   | Alerts | Base the SLI on alerts from integrated monitoring tools. Use alerts when you want your SLI to include early warning signs and a broader view of reliability. |
   | Outages | Base the SLI on outages detected by monitoring tools and reported by users. Use outages when you want to measure actual downtime and customer impact. |
   |-|-|

   {#sr-create-slo-sli__choicetable_bsn_r5m_dhc}  
   Hinweis:  
   If you create multiple SLIs for an SLO, they must use the same data source.
5. In the same form, select Add indicators for \<data source\>, fill in the fields for your SLI, and then select Next.  
   For more information about the SLI fields, see [Create SLI form](https://servicenow-prod.fluidtopics.net/Iv9BHBJR3XhwetkQVz1IjQ "Learn about the available fields for adding a service level indicator (SLI) to a service level objective (SLO).").
6. **Wahlweise:** In the Error budget policies form, select Add policy, and fill in the fields for your error budget policy.  
   For more information, see [Add an error budget policy form](https://servicenow-prod.fluidtopics.net/oopgZ9bw6gDo_WdLWH8rNg "Learn about the available fields for setting up error budget policies.").  
   Hinweis:  
   If you don't add an error budget policy, the SLO objective percentage is only informational. Adding a policy helps you take corrective actions based on the performance data. If you're not ready to add a policy, you can add one later.
7. Review your SLO, SLI, and error budget policy, and then select Activate.  
   Your SLO, SLI, and error budget policy are now active. The SLO record opens, displaying its reliability state and error budget information.
{#sr-create-slo-sli__steps_f41_jzv_r4b}

## Nächste Maßnahme

See the following to learn how to monitor and manage your SLOs:

* [Working with reliability metrics](https://servicenow-prod.fluidtopics.net/sixwTtdyj9W5yPw_gnhWRA "Learn about the reliability metrics and features that can help you track service health, respond to issues, and support business goals.") - Learn where and how to view SLO performance.
* [Edit a reliability metric](https://servicenow-prod.fluidtopics.net/WXXjLKmxmMU1uTdhxixysw "Update a reliability metric to keep it relevant and aligned with your team's goals.") - Update your SLOs to keep them aligned with your reliability goals.
{#sr-create-slo-sli__ul_jts_zzm_dhc}