--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Create SLO form # Create SLO form {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Create SLO form The Create SLO form in Service Reliability Management enables ServiceNow customers to define and configure Service Level Objectives (SLOs) to measure and manage service performance effectively. This form allows customers to specify key parameters that determine how service reliability is tracked, including the type of service level indicator (SLI), measurement methods, objectives, and compliance periods. Show full answer Show less ## Key Features * **Name:** Specify a unique identifier for the SLO. * **SLI Type:** Choose how to measure service performance, with options including: * Availability: Percentage of uptime. * Errors: Frequency of service errors. * Latency: Time taken to service requests. * Saturation: System resource utilization. * **Measurement Method:** Select between Duration (time without breach) or Count (number of occurrences/periods). Duration is the default and only option for some metrics. * **Objective (%):** Define the target availability or performance percentage (e.g., 99.999% uptime). * **Compliance Period:** Set the time frame over which metrics are calculated, with options for: * Month (calendar month) * Rolling 7 days * Rolling 30 days * Rolling 90 days * **Error Budget:** Automatically calculated based on the objective, representing the allowable downtime or errors. For duration measurements, it is expressed in days, hours, minutes, and seconds. * **Limit Occurrences (for Count-based SLOs):** Defines the maximum number of allowable breaches within the compliance period, acting as the error budget. * **Assignment Group:** Automatically populated to help align the SLO with responsible teams. ## Key Outcomes By using the Create SLO form, ServiceNow customers can precisely define service reliability targets aligned with business needs. The form's configurations help set clear expectations on service availability, error tolerance, and performance thresholds. Automated error budget calculations provide actionable insights into permissible service deviations, enabling proactive management and continuous improvement in service reliability. Learn about the available fields for adding a service level objective (SLO) to Service Reliability Management. ## Service level objective form {#sr-create-slo-sli-form__section_ehr_h2n_y1c} The following table describes the available options in the Service level objective form. For step-by-step instructions, see [Create SLOs, SLIs, and error budget policies](https://www.servicenow.com/docs/RUtZCPnk7cvZw7ea7LFYuw "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."). {#sr-create-slo-sli-form__id_sdb_v2n_y1c__entry__2} | Field | Description | |-|-| | Name | Name of the SLO. | | SLI type | * Availability: Percentage of time the service is available. * Errors: Frequency of service errors. * Latency: Time taken to service a request. * Saturation: Fullness of the system, focusing on resource use. {#sr-create-slo-sli-form__ul_vk4_nq1_s4b} | | How do you want to measure this objective? | You can measure this objective by: * Duration: The amount of time the service spends without breaching. It's the only value available. * Count: The number of periods or occurrences in a given compliance period. {#sr-create-slo-sli-form__ul_pwc_d3c_mzb} | [Table 1. Fields in the Service Level Objective form] {#sr-create-slo-sli-form__id_sdb_v2n_y1c} {#sr-create-slo-sli-form__id_xhm_y2n_y1c__entry__2} | Field | Description | |-|-| | Objective (%) | The percentage of how available (uptime) you want the service to be over a length of time. If measuring by duration, an objective percentage of Five Nines (99.999%) means the service was unavailable for 26 seconds per month, or about 5 minutes and 35 seconds per year. This value is used to calculate your error budget. | | Compliance period | Period for which the metrics are calculated. The available options are: * Month: The duration is considered to be the current month. For example, if the current date is 26th January, the duration will be considered from 1st January until 31st January.{#sr-create-slo-sli-form__slo_month} {#sr-create-slo-sli-form__slo_month} * Rolling 7 days: The duration is considered to be 7 days from the current date.{#sr-create-slo-sli-form__slo_rolling_7} {#sr-create-slo-sli-form__slo_rolling_7} * Rolling 30 days: The duration is considered to be 30 days from the current date. For example, if the current date is 26th January, the duration will be considered from 25th December.{#sr-create-slo-sli-form__slo_rolling_30} {#sr-create-slo-sli-form__slo_rolling_30} * Rolling 90 days: The duration is considered to be 90 days from the current date. For example, if the current date is 26th January, the duration will be considered from 25th October.{#sr-create-slo-sli-form__slo_rolling_90} {#sr-create-slo-sli-form__slo_rolling_90} {#sr-create-slo-sli-form__ul_nlx_4r1_s4b} | | Error budget | Auto-populated. The maximum level of errors (downtime) allowed over a certain period. A percentage of total service availability. Once you set your objective (%), your error budget is automatically calculated using this formula: 1 -- (Desired) Availability. The error budget of a service will be calculated in days, hours, minutes, and seconds for a desired availability of 99.99% (Four Nines) of the year by: 1. Calculating the total time in seconds in a year: 31536000 seconds. 2. Determining the error budget as 1 -- (Desired) Availability: 1 - 0.9999 = 0.0001. 3. Converting the error budget to time units. {#sr-create-slo-sli-form__ol_uwd_qnm_kbc} For example, if the error budget is 0.0001: * Error Budget in Seconds = 0.0001 \* 31,536,000 seconds = 3,153.6 seconds. * Error Budget in Minutes = 3,153.6 seconds / 60 = 52.56 minutes. * Error Budget in Hours = 52.56/60 = 0.875 hours. * Error Budget in Days = 52.56 minutes / (24 \* 60) ≈ 0.0364 days. {#sr-create-slo-sli-form__ul_iqm_wnm_kbc} Note: Your error budget appears in units of days, hours, minutes, and seconds only when you measure your SLO by duration. | [Table 2. Measuring by Duration] {#sr-create-slo-sli-form__id_xhm_y2n_y1c} {#sr-create-slo-sli-form__id_hnl_w2n_y1c__entry__2} | SLO type | Count by periods or Count by occurrences | |-|-| | Limit occurrences | The number of occurrences after which a breach occurs. Limit occurrences act as an error budget. | | Compliance period | Period for which the metrics are calculated. The available options are: * Month: The duration is considered to be the current month. For example, if the current date is 26th January, the duration will be considered from 1st January until 31st January. * Rolling 7 days: The duration is considered to be 7 days from the current date. * Rolling 30 days: The duration is considered to be 30 days from the current date. For example, if the current date is 26th January, the duration will be considered from 25th December. * Rolling 90 days: The duration is considered to be 90 days from the current date. For example, if the current date is 26th January, the duration will be considered from 25th October. {#sr-create-slo-sli-form__ul_wlr_12n_y1c} | [Table 3. Measuring by Count] {#sr-create-slo-sli-form__id_hnl_w2n_y1c} Note: The Assignment group is auto-populated.