Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
78 changes: 78 additions & 0 deletions solutions/observability/incident-management/slo-management.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,78 @@
---
navigation_title: View and manage SLOs
applies_to:
stack: ga
serverless:
observability: ga
products:
- id: observability
- id: cloud-serverless
---

# View and manage SLOs in {{product.observability}}

Manage your service level objectives (SLOs) from the **SLO Management** page. View SLO definitions, monitor the health of your SLOs, and perform actions such as editing, cloning, purging data, and deleting SLOs.

Check notice on line 14 in solutions/observability/incident-management/slo-management.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.Acronyms: 'SLO' has no definition.

To open the **SLO management** page:

Check notice on line 16 in solutions/observability/incident-management/slo-management.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.Acronyms: 'SLO' has no definition.

1. Navigate to the **SLOs** page in the main menu, or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
1. Select **Manage SLOs**.



## Filter SLOs

From the SLO Management page, use the search bar to find SLOs by name, or filter the list of SLOs by tag using the **Filter tags** dropdown menu.

## Monitor SLO health

Check notice on line 27 in solutions/observability/incident-management/slo-management.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.Acronyms: 'SLO' has no definition.
```{applies_to}
stack: ga 9.3
```

The **Health** column of the SLO management table shows the following:

* **Healthy**: the SLO transforms are operating as expected.
* **Needs attention**: the SLO transforms are not operating as expected and needs attention.

For more on SLO transforms and troubleshooting SLO health, refer to [Understanding SLO internals](../../../troubleshoot/observability/troubleshoot-service-level-objectives-slos.md#slo-understanding-slos).

Check notice on line 37 in solutions/observability/incident-management/slo-management.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.Acronyms: 'SLO' has no definition.

Check notice on line 37 in solutions/observability/incident-management/slo-management.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.Acronyms: 'SLO' has no definition.

Check notice on line 37 in solutions/observability/incident-management/slo-management.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.Acronyms: 'SLO' has no definition.

## Purge stale SLO instances

Check notice on line 39 in solutions/observability/incident-management/slo-management.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.Acronyms: 'SLO' has no definition.

A stale SLO instance hasn't received new data within the **Stale SLOs threshold**, which you can set in the **SLOs Settings**.

From the **Overview** on the **SLOs** page, you can see the number of **Stale** SLOs. Select the number to show your stale SLOs.

Occasionally, you might want to delete these stale instances. To purge your stale SLO instances:

Check notice on line 45 in solutions/observability/incident-management/slo-management.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.Acronyms: 'SLO' has no definition.

**Purge all stale SLO instances**

1. From the **SLO management** page, select **Actions** → **Purge stale instances**.

Check notice on line 49 in solutions/observability/incident-management/slo-management.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.Acronyms: 'SLO' has no definition.
1. If you don't want to delete stale instances according to the predefined **Stale SLOs threshold** setting, you can update the **Stale threshold**.
1. Select **Purge**.

**Purge stale instances from selected SLOs**

1. From the **SLO management** page, select the checkbox next to the SLOs from which you want to purge stale instances.
1. From the **Selected [number] SLO** menu, select **Purge stale instances**.
1. If you don't want to delete stale instances according to the predefined **Stale SLOs threshold** setting, you can update the **Stale threshold**.

Check notice on line 57 in solutions/observability/incident-management/slo-management.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.Acronyms: 'SLO' has no definition.
1. Select **Purge**.

## Purge SLO rollup data

Rollup functionality summarizes old, high-granularity data into a reduced granularity format for long-term storage.

Occasionally, you might want to delete this rollup data. To purge your rollup data:

**Bulk purge SLO rollup data**

1. From the **SLO management** page, select the checkbox next to the SLOs from which you want to purge rollup data.
1. From the **Selected [number] SLO** menu, select **Purge rollup data**.
1. Select the options to define which data to purge.
1. Select **Purge**.

**Purge rollup data from a single SLO**

1. Open the **Actions** menu ({icon}`boxes_vertical`) for the SLO.
1. Select **Purge rollup data**.
1. Select the options to define which data to purge.
1. Select **Purge**.
Loading