Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Fapm%2Ffeatures%2Fservice-slos.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Fapm%2Ffeatures%2Fservice-slos.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

# Service Level Objectives (SLOs)

## Overview[​](#overview "Direct link to Overview")

A Service Level Objective (SLO) is a measurable target that defines the acceptable performance or reliability level for a service, often expressed as a percentage (for example, 99% uptime or 95% request latency below a threshold). It represents an agreement between service providers and users on what "good enough" looks like.

### Why are SLOs essential for APM?[​](#why-are-slos-essential-for-apm "Direct link to Why are SLOs essential for APM?")

In APM (Application Performance Monitoring), SLOs help teams prioritize and measure the health of their services in a user-focused way. They enable:

* **Proactive issue management**: Highlight potential problems before they affect user experience.
* **Data-driven decisions**: Align engineering efforts with user expectations by focusing on what matters.
* **Efficiency**: Avoid over-investing in unnecessary reliability, balancing business needs and operational costs.
* **Accountability**: Provide clear, measurable goals to monitor and improve service performance.

## Creating an SLO[​](#creating-an-slo "Direct link to Creating an SLO")

APM SLOs are created through the SLO Center. Selecting **Add SLO** from a Service Catalog drilldown opens the SLO Center create drawer with the SLO type and service pre-filled for the service you are viewing.

1. From the **SLO** tab of a Service Catalog drilldown, select **Add SLO**. The SLO Center create drawer opens with the SLO type set to **APM** and the **Service** field pre-filled with the current service. Both fields are read-only.
2. Configure the SLO — name, description, owner, entity labels, filters, time frame, target, and (for Latency SLOs) time window, aggregation method, and query threshold. For the full field reference, see [Create SLOs](https://docs-docusaurus.kinsta.page/user-guides/slos/create/.md).
3. Select **Create** to save the SLO, or **Save & create alert** to create the SLO and immediately set up an alert based on it.

[![Create APM SLO](/assets/images/apm-slo-create-12d462bd69450de1c16f7ecef7f884d8.webp)](https://docs-docusaurus.kinsta.page/assets/images/apm-slo-create-12d462bd69450de1c16f7ecef7f884d8.webp)

After you save, the SLO Center opens with the new SLO in the list.

To open the SLO Center directly from the **SLO** tab without creating a new SLO, select **View in SLO Center**.

### SLOs view[​](#slos-view "Direct link to SLOs view")

Note

The **SLO** tab of each service lists the legacy APM SLOs defined for that service. SLOs created through the **Add SLO** button appear in the [SLO Center](https://docs-docusaurus.kinsta.page/user-guides/slos/view-and-manage-slo/.md), not in this list.

Each row represents a single legacy SLO, displaying its definition and status. The following columns are key to understanding the detailed status of your SLOs:

* **SLO Status**: Displays whether the SLO is in an "OK" or "Breached" state based on its current state and remaining errors budget.
* **SLO Name**: The name of the SLO as provided during its creation.
* **Threshold**: Specifies the allowable limit for each of the measured events. For SLOs on errors, the threshold is `Is Error`. For SLOs on latency, the threshold is the maximum allowed duration.
* **Time**: The defined evaluation period for the SLO, such as 7 days, 30 days.
* **Target**: Displays the predefined SLO target.
* **Current State**: Displays the real-time SLO status based on actual calculations.
* **Remaining Budget**: Displays the percentage of the allowable error or latency threshold remaining, along with a visual consumption bar. Your error budget is the allowable number of errors or latency threshold violations. The remaining budget shows the percentage left from this budget, with a visual bar indicator reflecting the budget consumption.

### Error budget consumption bar[​](#error-budget-consumption-bar "Direct link to Error budget consumption bar")

A color bar visualizes of the error budget consumption and provides an at-a-glance overview of the current state of your error budget, helping you quickly assess the health of your SLOs.

By combining these metrics and visual indicators, the SLOs tab offers a comprehensive view of your service-level objectives, empowering you to monitor and manage them effectively.

* **Green**: 75%-100% of the allowed budget remaining.
* **Yellow**: 25%-75% of the allowed budget remaining.
* **Orange**: 0%-25% of the allowed budget remaining.

### SLO drilldown[​](#slo-drilldown "Direct link to SLO drilldown")

1. Select the SLO to get real-time tracking of SLO events (spans) that affects your remaining SLO budget.

2. Select the event to view an example of the traces where the threshold violation occurred.

Note

* Only [team admins](https://docs-docusaurus.kinsta.page/user-guides/account-management/user-management/create-and-manage-teams/.md) can add new SLOs.
* New SLOs take at least seven days for their computation window to complete.
* Until completed, the SLO will display incomplete data.

### SLO calculation example[​](#slo-calculation-example "Direct link to SLO calculation example")

* **SLO target**: 99%. The target is set to ensure that 99% of requests meet the defined success criteria over a 7-day period.

* **Current state**: 99.48%. Based on the data for the last 7 days:

  <!-- -->

  * **Total Requests**: 10,000
  * **Threshold Violations**: 52

[![](/assets/images/formula-1-e126e0b9a7e6fbe726961160cc2fc747.webp)](https://docs-docusaurus.kinsta.page/assets/images/formula-1-e126e0b9a7e6fbe726961160cc2fc747.webp)

* **Remaining budget**: 48%

  The error budget defines the allowable number of threshold violations within the 7-day period.

  * **Allowed Violations**: 100 (1% of 10,000 requests)
  * **Remaining Violations**: 48 (100 - 52 violations)

[![](/assets/images/formula-2-60a1b8f836685667d4ea597fa1ec896c.webp)](https://docs-docusaurus.kinsta.page/assets/images/formula-2-60a1b8f836685667d4ea597fa1ec896c.webp)

### Additional resources[​](#additional-resources "Direct link to Additional resources")

|                   |                                                                                                                                 |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Coralogix Academy | [SLO/SLI Management in Coralogix APM](https://coralogix.com/academy/get-to-know-coralogix/slo-sli-management-in-coralogix-apm/) |
| API               | [SLO Management API](https://docs-docusaurus.kinsta.page/developer-portal/apis/data-management/slo-management-api/.md)          |
| Terraform         | [Terraform registry](https://registry.terraform.io/providers/coralogix/coralogix/latest/docs/resources/slo)                     |

## Next steps[​](#next-steps "Direct link to Next steps")

When an SLO breaches, jump to [Analyze](https://docs-docusaurus.kinsta.page/user-guides/apm/features/analyze/.md) to see which dependencies and traces are driving the regression.